Roadmap search

Versions, deliverables, workstreams, tasks, and pages

Beskid

Jump to a Beskid service

HomeSpecificationBookpckgTrackerNexus
← CatalogView on beskid-lang.org

Diagnostics parity (CLI and LSP) - Design model

articleStandard

src/content/docs/platform-spec/compiler/build-pipeline/diagnostics-parity/design-model.mdx

import SpecArticleChrome from '@beskid/beskid-ui/platform-spec/SpecArticleChrome.astro';

<SpecArticleChrome />

Parity is defined at semantic meaning, not identical text formatting. CLI and LSP must use the same ProgramAssembly discovery mode policy (closure for build/run; workspace scan for IDE project diagnostics when a compile plan exists).

  • CLI parse diagnostics are path-anchored for user files.
  • Lowering parse diagnostics may use synthetic source names.
  • LSP has cold-parse and warm-snapshot paths but must align on rule outcomes.