The next generation of tooling for Spring Boot, including support for Cloud Foundry manifest files, Concourse CI pipeline definitions, BOSH deployment manifests, and more... - Available for Eclipse, Visual Studio Code, and Theia
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.
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.