Extension UX.
FAQ and troubleshooting
Platform spec article
FAQ and troubleshooting
Spec standingStandard
-
Four views
Context
Decision
Four views under one container.
Consequences
beskid_vscode runtime.
Verification anchors
package.json; runtime tests.
-
focusedProjectUri
Context
Extension UX.
Decision
Single focus drives outline and packages.
Consequences
beskid_vscode runtime.
Verification anchors
package.json; runtime tests.
-
pckgClient only
Context
Extension UX.
Decision
Registry HTTP via pckgClient only.
Consequences
beskid_vscode runtime.
Verification anchors
package.json; runtime tests.
-
LSP graph only
Context
Extension UX.
Decision
Graph via LSP executeCommand only.
Consequences
beskid_vscode runtime.
Verification anchors
package.json; runtime tests.
-
Status controller
Context
Extension UX.
Decision
One status bar for LSP, pckg, CLI.
Consequences
beskid_vscode runtime.
Verification anchors
package.json; runtime tests.
- Contracts and edge cases focusedProjectUri, LSP executeCommand JSON, auth, and offline registry behavior.
- Design model Extension layout, focus model, and status-bar phases for the Beskid VS Code extension.
- Examples corelib workspace and single-app project scenarios.
- FAQ and troubleshooting Common questions about focus, private registries, offline mode, and LSP restarts.
- Flow and algorithm Activation through LSP init, tree refresh, and package search.
- Verification and traceability Tests, CI, and smoke checks for the VS Code extension surface.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| 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).
Purpose and scope
Section titled “Purpose and scope”Operator and contributor FAQ for the extension surface and linked features.
Why do Workspaces and Project show different roots?
Section titled “Why do Workspaces and Project show different roots?”Workspaces lists every Workspace.proj under VS Code folders. Project shows only the focused Project.proj DAG. Standalone apps may leave Workspaces empty while Project still works after auto-select.
The LSP restarted when I clicked a member — is that expected?
Section titled “The LSP restarted when I clicked a member — is that expected?”No. Focus changes must use configuration notification only. If a full restart occurs, file a bug against extension runtime wiring.
Registry search returns 401
Section titled “Registry search returns 401”Configure Beskid: Set Package Registry API Key (stores in VS Code secret storage). For human browsing, open the pckg web dashboard in a browser (login is out of band for the extension in v0.2).
Packages show declared but not locked versions
Section titled “Packages show declared but not locked versions”Run Lock from the Packages view title or beskid lock in the terminal. Ensure Project.lock exists beside Project.proj per workspace and lock contracts.
beskid command not found for Fetch/Lock
Section titled “beskid command not found for Fetch/Lock”Set beskid.cli.path to the absolute CLI binary (for example from downloads or cli-latest release).
Offline development
Section titled “Offline development”LSP and This project work offline. Registry search requires network; cached hits may appear until TTL expiry.
Where are executeCommand JSON schemas defined?
Section titled “Where are executeCommand JSON schemas defined?”Canonical schemas live in workspace and project explorer — contracts. LSP tests should golden-match those shapes.