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

    Adapter that exposes the VSX extensions model as a generic ExtensionsSourceContribution.

    The model continues to own all VSX-specific state (OVSX search, plugin server lifecycle, recommendations). This adapter is a thin translation layer that lets the Extensions view query VSX entries through the same contribution mechanism as MCP servers and future artifact types.

    Implements

    Index

    Constructors

    Properties

    displayName: string = ...

    Human-readable label used as the group header in the view.

    priority: 0

    Ordering hint when multiple contributions yield entries for the same section. Lower numbers come first. Defaults to 0.

    searchToken: "@extensions" = '@extensions'

    @-prefixed token recognised in the search query to scope results to this contribution alone. Composable with the existing @installed / @builtin / @recommended mode tokens (e.g. @installed @mcp shows installed servers of type mcp-server only). When no type token appears in the query, all contributions are shown.

    Contributors are expected to start the token with @; without the prefix the search model may treat the token as a plain word in the free-text part of the query.

    type: "extension" = 'extension'

    Stable, machine-readable identifier for the artifact type.

    Accessors

    Methods

    • Entries matching a user search. Each result carries its own searchableText so the view can rank hits from all contributions against a single query. Omit if this type does not participate in search.

      Contributions may ignore query when their internal state already reflects the current query (e.g. the VSX adapter, whose model is kept in sync with the search bar via the singleton VSXExtensionsSearchModel). In that case the contribution is expected to yield its current result set and let the view's cross-contribution fuzzy ranker handle the actual ordering.

      Returns Iterable<SearchResult>