Describe the bug
Moving/renaming a module via the file explorer triggers a rename of the qualified references to this module. This rename does not consider Tutor concept links, since they are technically comments/layout, hence breaking Tutor builds.
To Reproduce
Steps to reproduce the behavior:
- Consider a module with a concept link to itself.
module M
@synopsis{Definition of ((M::D)).}
data D = d();
- Rename the module to
M2 in the file explorer.
- Observe the module header change, but not the concept link.
Desktop (please complete the following information):
- Context: VS Code extension
- Rascal Version: Rascal-LSP
2.22.1
Describe the bug
Moving/renaming a module via the file explorer triggers a rename of the qualified references to this module. This rename does not consider Tutor concept links, since they are technically comments/layout, hence breaking Tutor builds.
To Reproduce
Steps to reproduce the behavior:
M2in the file explorer.Desktop (please complete the following information):
2.22.1