spring-projects / spring-projects/spring-tools
take Java search scope into account
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
The Java tooling for VSCode introduced a search scope a while ago:
https://github.com/redhat-developer/vscode-java/issues/2649
https://github.com/gayanper/vscode-java/commit/a34e5c557f83ee4bc38a6c14be1888175fd98694
https://github.com/eclipse-jdtls/eclipse.jdt.ls/issues/3252
This basically allows operations like find references or show hierarchy to focus the results on either all the java sources or from sources excluding test cases.
The idea here would be to take this search scope into account as well for symbols, find references, etc. It would mean that we need to get information from the Java extension about the current search scope (and updates about that setting), and take that information into account. It would either require us to take this scope into account when indexing source code or to filter out test folders from results.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked VSCode Java issues and commit to understand the search-scope setting and its updates. Trace the existing entry points for symbols, find references, and related results, then determine whether scope belongs in source indexing or result filtering; done means those operations honor the selected Java source scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- developer-experience, search, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100