✨ add ability to set search scope by file paths #94
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
Signed-off-by: Pranav Gaikwad <[email protected]>
shawn-hurley
approved these changes
May 13, 2024
Signed-off-by: Pranav Gaikwad <[email protected]>
|
@shawn-hurley @jmle hey folks, I am going to test this PR with analyzer-lsp, I added test cases there. If that PR passes, we should be good with this change. |
This was referenced Jun 22, 2024
This was referenced Jul 30, 2024
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 adds ability to create a search scope from file paths, and also disables test files from scope (this is the first true argument to createSearchScope function). Note that the search scope can only be set at a package level. Haven't yet figured out how to get it down to compilation units. But I think this is enough for now.