Design model

Platform spec article

Design model

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

Activity bar layout

View ID	Purpose
beskidWorkspaceView	All Workspace.proj trees and members
beskidProjectView	Focused Project.proj targets, dependencies, sources
beskidProjectOutlineView	Document symbols for .bd under focused project
beskidPackagesView	This project + registry search

Focus model

• Focused project — one Project.proj URI drives LSP focusedProjectUri, CLI cwd, and the This project package section.
• Auto-select — when beskid.project.autoSelectFromEditor is true, the active editor selects the nearest project manifest.
• Override — beskid.selectProject quick pick remains available.

Status bar phases

Phase	Source
workspace_scan	LSP notification beskid/status
search / details	pckg HTTP
fetch / lock / build / test / analyze	CLI runner

Implementation: beskid_vscode/src/status/beskidStatusController.ts, FocusCoordinator, slim BeskidExtensionRuntime.