Repository navigation
Description
The server's settings, written in t27's own format. A language that asks users to describe their tooling in somebody else's schema has not shipped its tooling. The settings, their types and defaults are one .t27 module; the VS Code package.json section and the settings documentation are generated from it. A project can set the same values in a .t27 module at its root, merged by condition the way clangd merges .clangd fragments. Part of the LSP epic, Refs #12209 (wave 2, beyond the standard). Only .t27: no code in any other language, not even scratch probes or a loader; see skill only-t27.
Depends on specs/lsp/workspace.t27 (where the values arrive from). Rule: the truth lives here once, and generated files point at it (own-language-first, and the rule against hand-copied lists).
Prior art:
- clangd
.clangdfragments withIf: PathMatchconditions, merged over user and project config: https://clangd.llvm.org/features - rust-analyzer: every setting documented in one place, generated from the source: https://rust-analyzer.github.io/book/configuration.html
- gopls settings by group, with defaults and a stability label per setting: https://go.dev/gopls/
Boundary
- specs/lsp/config.t27
User Scenarios
- Given a setting
inlayHints.typesis declared once in the module with a type, a default and a doc line, whent27c gen-jsonruns on the module, then the output contains thecontributes.configurationentry for the VS Code client, and no second hand-written copy exists. - Given a project file
t27.config.t27withif path_match("specs/numeric/**") { check.onSave = "lint" }, when a file under that path is saved, then the value islintthere and the default elsewhere. - Given an unknown key in the project file, when it is read, then the server publishes a diagnostic on the key, naming the nearest known key.
- Given a value of the wrong type, when it is read, then the value is ignored, the default stands, and a diagnostic says why.
- Given the settings page, when it is generated, then it lists every setting with type, default, doc and stability (
stable,experimental).
Requirements
- FR-001: The module MUST declare every setting of every LSP module in one table (key, type, default, doc, stability) and MUST provide
get(key, scope)andmerge(layers). - FR-002: Layers MUST merge in the documented order: built-in defaults, user, project file, client settings; a test asserts the order with values that differ in each layer.
- FR-003: The project file MUST be a
.t27module the compiler accepts, with conditional blocks on path patterns; the module defines the condition syntax in its header. - FR-004: Unknown keys, wrong types and out-of-range values MUST produce diagnostics on the project file and MUST NOT stop the server.
- FR-005: The module MUST not be copied: the VS Code settings and the docs page are generated from it (
gen-json,gen-mdor the equivalent t27c output), and a gate compares the generated file with a fresh generation.
Success Criteria
- At least 25 tests in
specs/lsp/config.t27pass, run on the lab witht27c test-report(exit 0), including merge order and all three error kinds. - The generated
contributes.configurationJSON for the table is produced on the lab by onet27ccommand, whose exact text is pasted in the issue; if the generator cannot express it, a compiler gap is filed on epic: self-host t27c -- rewrite the compiler from Rust into t27 #5980 with a minimal.t27repro and this issue links it. git diff --name-only masterlists onlyspecs/lsp/config.t27and generated files named in the issue (0 hand-written files in other languages).
Activity
gHashTag commentedon Nov 17, 2026
Spec created: specs/lsp/config.t27 (typecheck OK, 2 tests pass).
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Spec exists and passes typecheck + tests. M5 milestone complete.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.