@kkdev92/vscode-ext-kit - v4.1.1
    Preparing search index...

    Interface RawRegistrationContext

    What a raw registration is given.

    Deliberately does not hand over a substitutable vscode object: the framework cannot fake an arbitrary VS Code API, so pretending otherwise would misrepresent what a Test Host guarantees. Import vscode directly and put each returned registration or cleanup into the appropriate Module scope below. The Test Host can verify lifecycle and portable collaborators; behavior that calls the real vscode module still needs Extension Host integration coverage.

    interface RawRegistrationContext {
        logger: Logger;
        registrations: RegistrationScope;
        resources: ResourceScope;
        services: ServiceResolver;
    }
    Index
    logger registrations resources services
    logger: Logger

    Logger scoped to this registration.

    registrations: RegistrationScope

    Module RegistrationScope, shared with the Module's other registrations. Own native registrations here so stop closes their ingress synchronously.

    resources: ResourceScope

    Module ResourceScope, shared by every raw registration in the Module. Own resource cleanup here; prefer deferAsync when the teardown is a promise-returning callback, so the registration site says so.

    services: ServiceResolver

    Resolves from the Application container, with disposable transients owned by the Module ResourceScope above. Prefer the injected argument for actual dependencies so preflight can validate the declared graph; reserve this resolver for genuinely dynamic lookup.

    Settings
    Member Visibility

    On This Page
    Properties