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) - Contracts and edge cases

articleStandard

src/content/docs/platform-spec/compiler/build-pipeline/diagnostics-parity/contracts-and-edge-cases.mdx

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

<SpecArticleChrome />
  • Semantic error presence/absence must match across CLI and LSP for equivalent source.
  • Source label differences are allowed when paths intentionally differ (path, source.bd, "<memory>").
  • Manifest (.proj) diagnostics must use project-error mapping paths, not code-file parsers.
  • Snapshot reuse in LSP must not hide newly introduced semantic errors.