Rename refactoring incorrectly renames references to declarations that were imported under an alias

[lars-reimann]

Describe the bug

Renaming a declaration updates the $reftext of all references to that declaration, even if the declaration was imported under an alias.

To Reproduce

Example code:

// file1.sdstest
package package1

class C

// file2.sdstest
package package2

from package1 import C as D

fun f(p: D)

1. Rename class C to E
2. The code in file2.sdstest now changes to

// file2.sdstest
package package2

from package1 import E as D

fun f(p: E)

This no longer compiles

Expected behavior

Only the import should be updated:

// file2.sdstest
package package2

from package1 import E as D

fun f(p: D)

We could ensure that the $reftext is equal to the declaration name.

This is not good enough, since we might also have this code in file2.sdstest:

// file2.sdstest
package package2

from package1 import C as C

fun f(p: C)

Now the $refText matches the declaration name, but it should still not be changed. We generally need to check whether a declaration was imported using an alias.

Screenshots (optional)

No response

Additional Context (optional)

No response

[lars-reimann]

🎉 This issue has been resolved in version 0.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• v0.6.0
• GitHub release

Your semantic-release bot 📦🚀