02.2 VS Code and LSP
Beskid VS Code extension, language ids, Open VSX install, and LSP binary selection.
VS Code and LSP
The fastest way to hate a new language is an editor that treats your files as plain text with extra steps.
Install the extension
Section titled “Install the extension”Published on Open VSX: beskid-vscode.
The extension registers:
beskidfor*.bdsourcesbeskid-projfor*.projmanifests (highlighting + the same LSP project model)
Bundled vs local LSP
Section titled “Bundled vs local LSP”You can run the bundled language server (matches the extension release) or point settings at a local development binary built from compiler/. Use local when you are hacking the compiler; use bundled when you are writing Beskid apps.
Mismatch symptoms:
- Parse OK in terminal, squiggles nonsense in editor
- Fixes apply in CLI but not after save in IDE
Fix: align beskid --version with the LSP binary the extension launches.
What LSP gives you (week one)
Section titled “What LSP gives you (week one)”- Diagnostics on save / open
- Basic navigation hooks (exact feature set grows with the server—see LSP architecture)
- Project-aware analysis rooted at
Project.proj
Deep reference
Section titled “Deep reference”- Guides / LSP
- Platform spec — tooling / editor integration (as indexed in platform-spec)