Examples

Platform spec article

Examples

Back to Workspace and project explorer ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (2)

1. 0001-lsp-backed-graph LSP graph Accepted

   LSP graph

   Context

   Parser drift.

   Decision

   Graph via LSP executeCommand.

   Consequences

   Thin wrappers.

   Verification anchors

   beskid_lsp handlers.

   Open full ADR page

2. 0002-focus-without-lsp-restart Focus without restart Accepted

   Focus without restart

   Context

   UX on focus.

   Decision

   didChangeConfiguration for focus; no LSP restart.

   Consequences

   Fast focus switch.

   Verification anchors

   Session invalidation.

   Open full ADR page

Articles

• Contracts and edge cases focusedProjectUri, LSP executeCommand JSON schemas, and explorer edge-case rules. article Standard Reviewed Thu May 21
• Decisions record (legacy index) Migration index for workspace and project explorer ADRs. article Standard Reviewed Fri May 22
• Design model Tree item model, focus state, icons, and multi-root labeling for workspace and project explorers. article Standard Reviewed Thu May 21
• Examples Corelib workspace and single-application explorer scenarios. article Standard Reviewed Thu May 21
• Flow and algorithm Activation, LSP init, tree refresh, auto-select, and reveal flows for workspace and project explorers. 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 · 7 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
  Workspace and project explorer

  Parent feature hub

Purpose and scope

Representative explorer behavior for the corelib workspace and a single-app folder opened without a workspace manifest.

Corelib workspace

Setup: Open folder compiler/corelib/ containing Workspace.proj named corelib with multiple members under packages/.

Expected Workspaces view:

• One workspace root labeled corelib (or corelib / corelib when multi-root).
• Member children for each Workspace.proj entry (for example collections, query, system).
• Optional node workspace.package.json when present at workspace root.

User action: Click member collections.

Expected:

• focusedProjectUri → file://…/packages/collections/Project.proj
• Project view root shows collections targets and dependencies from beskid.getProjectGraph
• beskid.getProjectDependencies returns locked versions after beskid lock has been run in that workspace

Smoke checklist:

1. All members listed match Workspace.proj without manual refresh.
2. Editing Project.lock triggers debounced refresh; locked versions update in Project tree tooltips.
3. beskid.refreshWorkspace from palette completes without LSP restart.

Single-application project

Setup: Open folder containing only Project.proj (no parent Workspace.proj), e.g. a console app template output.

Expected Workspaces view:

• Empty state: “No Beskid workspaces found” (or equivalent localized string).
• User may still focus via Project picker or auto-select.

Expected Project view:

• Root = the lone Project.proj
• Dependencies from getProjectGraph; unresolved registry deps show warning icon until beskid fetch

Auto-select: Opening Src/Main.bd sets focus to the containing Project.proj when beskid.project.autoSelectFromEditor is true.

Multi-root VS Code workspace

Setup: VS Code workspace with folders corelib/ and my-app/ side by side.

Expected labeling:

• corelib / collections vs my-app / my-app member labels to disambiguate.

Focus: Switching editors between folders updates focus per auto-select rules without mixing dependency graphs.

Related topics

• Extension surface examples
• Workspace and lock contracts