Repository navigation
Use declaration URIs for call and type hierarchy items - #2280
Merged
msujew merged 1 commit intoNov 19, 2026
Merged
Conversation
msujew
approved these changes
Nov 19, 2026
msujew
left a comment
Member
There was a problem hiding this comment.
Oh, what an oversight. Thanks!
Contributor
Author
|
Thanks for merging this! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If you open the type hierarchy from a reference in another file, the list of supertypes can be empty. Opening it from the declaration shows the parent as expected.
The hierarchy item had the declaration’s range but the reference file’s URI, so Langium looked up the range in the wrong file. The call hierarchy provider had the same bug. Both now use the declaration’s URI.