Skip to content

Improve Ctrl+T (# symbol search) result ranking by prioritizing project symbols over library symbols #3789

Description

@milic-marko

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:

#RequestHandler

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions