Improve document symbols #1848
Merged
Improve document symbols #1848
Conversation
This file contains 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
yannham
approved these changes
Mar 12, 2024
| let children = field.value.map(|v| symbols(world, type_lookups, &v)); | ||
|
|
||
| #[allow(deprecated)] | ||
| // because the `deprecated` field is... wait for it... deprecated. |
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.
This changes the "document symbols" request to something that I think is more useful: it lists only "publicly visible" symbols, by which I mean symbols that someone importing the file can access using field paths. In particular, local let bindings are no longer included, nor are fields in records that are only visible in local function bodies and let bindings.
The symbols are also presented hierarchically now.
Fixes #1627