fix: respect includeDeclaration in references#191
Merged
Conversation
|
Docs preview: https://vide.pascal-lab.net/preview/pr-191/ |
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.
Closes #184.
Although the PR title uses
fix, I don't really treat this as a symbol-resolution bug. Reference search itself was already working, but thetextDocument/referenceshandler did not properly honorReferenceContext.includeDeclaration.That alone is not enough to change VS Code's default behavior, because VS Code's references flow requests declaration-inclusive results by default. For users who prefer usages-only results, this PR adds a client-side setting that overrides the request context before sending it to the language server.
Changes
ReferenceContext.includeDeclarationfortextDocument/referencesUser-facing behavior
By default, references remain declaration-inclusive.
Users who want usages-only results can set:
{ "vide.references.includeDeclaration": false }