Theia API Documentation v1.73.0
    Preparing search index...

    Relevance filter shared by the MCP-server and skill contributions to the Extensions view.

    The shared Extensions ranker fuzzy-matches scattered characters across a combined searchable text. Registry descriptions are long, keyword-rich prose, so that match treats almost every entry as a hit for any short query (e.g. asana matching every server). This filter narrows the candidate set to genuine matches before the shared ranker runs.

    An entry matches when every whitespace/punctuation-separated query term either:

    • appears as a substring of the meaningful name or identifier (so asana matches com.asana/mcp and art matches algorithmic-art), or
    • is the prefix of some word in the name, identifier or description (so powerpoint finds an entry whose description mentions "PowerPoint").

    Exposed as an injectable service so adopters can rebind it to tweak search semantics for their registry contributions.

    Index

    Constructors

    Methods

    • Reduces a registry identifier to its human-meaningful part for search matching.

      Registry identifiers are reverse-DNS ids with a path, e.g. com.asana/mcp or io.github.anthropics/algorithmic-art. The leading domain labels (com, io, github, ...) are shared boilerplate that would otherwise let a query like git match every io.github.* entry. This keeps only the last domain label plus the path: asana mcp, anthropics algorithmic-art.

      Plain strings without a domain or path are returned unchanged.

      Parameters

      • identifier: string

      Returns string