When using symbol search via Ctrl+T in VS Code with Eclipse JDT LS, searching with # currently returns a mixed list of symbols from both the current workspace/project and external libraries/dependencies.
For large projects with many dependencies, relevant project symbols are often buried under symbols originating from libraries, making navigation slower and noisier.
It would be helpful if search results were ranked by relevance, with symbols/classes from the current workspace prioritized above symbols from external libraries.
Current Behavior
Searching for symbols using Ctrl+T and #:
- Returns symbols from:
- current workspace/project
- external JARs/dependencies
- JDK classes
- Results appear intermixed
- Exact or highly relevant project symbols may appear below dependency/library matches
Example:
Searching for:
May produce results like:
org.springframework...RequestHandler
some.library...RequestHandler
my.project.api.RequestHandler
even though the project-local symbol is usually the most relevant result.
When using symbol search via
Ctrl+Tin VS Code with Eclipse JDT LS, searching with#currently returns a mixed list of symbols from both the current workspace/project and external libraries/dependencies.For large projects with many dependencies, relevant project symbols are often buried under symbols originating from libraries, making navigation slower and noisier.
It would be helpful if search results were ranked by relevance, with symbols/classes from the current workspace prioritized above symbols from external libraries.
Current Behavior
Searching for symbols using
Ctrl+Tand#:Example:
Searching for:
May produce results like:
even though the project-local symbol is usually the most relevant result.