Index declarations as symbols for LSP symbol search #87
Conversation
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
1 participant
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.
Index procedure declarations as "symbols" in the language server, making them available for document and project-wide symbol searches.
Among other things this involved a bit of cleanup in the initialization code path, and exposing the
textDocument/documentSymbolandworkspace/symbolcapabilities.To facilitate project-wide symbol search by a user, we add a cache and populate it with symbols from all Technique files in the local project. The ignore crate is used so that files ignored by e.g. .gitignore are omitted when searching.
Procedure declarations are sent as
SymbolKind::CONSTRUCTOR, matching the context used in syntax highlighting.