You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Vocabulary: core reads guarantees, facts, encodings, annotations and settings keys from it #221
From generation#137 (closed): when the catalog gets its diagnostics kind, the generation checks' codes need to move into it as well as core's. They are pub consts in comline_codegen::checks: generation::async-unused, generation::no-package-connection, generation::ignored-feature, generation::method-name-clash and generation::no-connection-protocols (info). The specification's compiler cases also keep their own closed code list in specs/compiler.cue (import::bare-own-schema-path, import::unresolved, unverified::*) that moves with them (see specification#12).
Audit 2026-11-16: ticked the three parts core#236 did (Guarantee names and descriptions, facts and their value domains, official encodings with their aliases and spellings, all read from the specification's comline-catalog). Still open: annotation names and settings keys (refusing unknown ones, #171 and #178), and diagnostic codes with explanations; the catalog has no such kinds yet (specification/catalog/schema.cue). Removed the stale blocked label: #220 is closed and the catalog lives in the specification repository.
From #10 (narrowed): it also wanted a reference page of diagnostic codes, generated so it can't drift from the code (each code, its meaning, how to fix it). That fits this issue's last box (diagnostic codes with explanations for the CLI and the language server); once codes live in the catalog the page can be generated from it.
Activity
Kinflou commentedon Nov 15, 2026
From generation#137 (closed): when the catalog gets its diagnostics kind, the generation checks' codes need to move into it as well as core's. They are pub consts in comline_codegen::checks: generation::async-unused, generation::no-package-connection, generation::ignored-feature, generation::method-name-clash and generation::no-connection-protocols (info). The specification's compiler cases also keep their own closed code list in specs/compiler.cue (import::bare-own-schema-path, import::unresolved, unverified::*) that moves with them (see specification#12).
Kinflou commentedon Nov 15, 2026
Audit 2026-11-16: ticked the three parts core#236 did (Guarantee names and descriptions, facts and their value domains, official encodings with their aliases and spellings, all read from the specification's comline-catalog). Still open: annotation names and settings keys (refusing unknown ones, #171 and #178), and diagnostic codes with explanations; the catalog has no such kinds yet (specification/catalog/schema.cue). Removed the stale blocked label: #220 is closed and the catalog lives in the specification repository.
Kinflou commentedon Nov 15, 2026
From #10 (narrowed): it also wanted a reference page of diagnostic codes, generated so it can't drift from the code (each code, its meaning, how to fix it). That fits this issue's last box (diagnostic codes with explanations for the CLI and the language server); once codes live in the catalog the page can be generated from it.