Skip to content

Vocabulary: core reads guarantees, facts, encodings, annotations and settings keys from it #221

Open

Description

@Kinflou

Part of #219, proposal ComlineProject/docs#162 (rollout stage 2). Blocked on #220.

Core reads the vocabulary instead of its own copies:

A package's own encoding declarations in config.idp merge in with the same shape, and the same rules judge them.

Activity

  1. added
    P2Soon
    diagnosticsErrors and diagnostics
    blockedWaiting on something else
    configPackages, config.idp, settings
    on Nov 9, 2026
  2. moved this from Todo to Blocked in Comline Development Roadmapon Nov 15, 2026
  3. Kinflou commented on Nov 15, 2026

    @Kinflou
    MemberAuthor

    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).

  4. Kinflou commented on Nov 15, 2026

    @Kinflou
    MemberAuthor

    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.

  5. Kinflou commented on Nov 15, 2026

    @Kinflou
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2SooncompilerParser, IR, CASconfigPackages, config.idp, settingsdiagnosticsErrors and diagnostics

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions