Flow and algorithm

Platform spec article

Flow and algorithm

Back to Extension surface ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (5)

1. 0001-four-activity-bar-views Four views Accepted

   Four views

   Context

   Extension UX.

   Decision

   Four views under one container.

   Consequences

   beskid_vscode runtime.

   Verification anchors

   package.json; runtime tests.

   Open full ADR page

2. 0002-focused-project-uri focusedProjectUri Accepted

   focusedProjectUri

   Context

   Extension UX.

   Decision

   Single focus drives outline and packages.

   Consequences

   beskid_vscode runtime.

   Verification anchors

   package.json; runtime tests.

   Open full ADR page

3. 0003-pckg-client-only-http pckgClient only Accepted

   pckgClient only

   Context

   Extension UX.

   Decision

   Registry HTTP via pckgClient only.

   Consequences

   beskid_vscode runtime.

   Verification anchors

   package.json; runtime tests.

   Open full ADR page

4. 0004-lsp-graph-data-only LSP graph only Accepted

   LSP graph only

   Context

   Extension UX.

   Decision

   Graph via LSP executeCommand only.

   Consequences

   beskid_vscode runtime.

   Verification anchors

   package.json; runtime tests.

   Open full ADR page

5. 0005-shared-status-controller Status controller Accepted

   Status controller

   Context

   Extension UX.

   Decision

   One status bar for LSP, pckg, CLI.

   Consequences

   beskid_vscode runtime.

   Verification anchors

   package.json; runtime tests.

   Open full ADR page

Articles

• Contracts and edge cases focusedProjectUri, LSP executeCommand JSON, auth, and offline registry behavior. article Standard Reviewed Thu May 21
• Design model Extension layout, focus model, and status-bar phases for the Beskid VS Code extension. article Standard Reviewed Thu May 21
• Examples corelib workspace and single-app project scenarios. article Standard Reviewed Thu May 21
• FAQ and troubleshooting Common questions about focus, private registries, offline mode, and LSP restarts. article Standard Reviewed Thu May 21
• Flow and algorithm Activation through LSP init, tree refresh, and package search. article Standard Reviewed Thu May 21
• Verification and traceability Tests, CI, and smoke checks for the VS Code extension surface. article Standard Reviewed Thu May 21

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 14 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
what-this-feature-specifies	yes	yes
implementation-anchors	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Extension surface

  Parent feature hub

Activation sequence

1. extension.ts constructs BeskidExtensionRuntime.
2. Register tree providers, commands, task providers, file watchers.
3. Start LanguageClient with focusedProjectUri from workspace state.
4. initialized → LSP workspace scan → beskid/status progress.
5. beskid.listWorkspaces populates Workspaces view.

Package search flow

1. User runs Search packages or view welcome link → InputBox.
2. Provider debounces 300ms, calls cached GET /api/search.
3. Registry rows expand → GET /api/packages/{name} for versions/deps.
4. Fetch / Lock view title → beskidCliRunner → refresh This project via beskid.getProjectDependencies.

Watchers

Glob: **/{*.bd,*.proj,Project.lock,workspace.package.json} → debounced beskid.refreshWorkspace + tree refresh.