You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
For features implemented in #645 and #648, they only work for import but not include, for specifically, the do_rename_file function only consider import as dependency not include.
When renaming a include, the file will be rename, but not the symbol.
pubstructModuleDependency{/// The dependencies of this module.pubdependencies:EcoVec<TypstFileId>,/// The dependents of this module.pubdependents:EcoVec<TypstFileId>,}
considers only import, but not include, the question is should we include include in this struct, and collects with import?
The module dependencies only refer to the relations affecting code analysis, therefore the include paths are not taken into account. In fact, there are also need to rename with regard to other paths within source files, like paths in #image or #bibliography calls. We may solve them all together.
I got it, include is more similar to #image or #bibliography, however, when I rename on an #include, it will rename the file, I hope to temporarily disable this feature before the feature is fully implemented.
Describe the bug
For features implemented in #645 and #648, they only work for import but not include, for specifically, the
do_rename_file
function only consider import as dependency not include.When renaming a include, the file will be rename, but not the symbol.
Package/Software version:
The text was updated successfully, but these errors were encountered: