mirror of
https://github.com/earendil-works/pi.git
synced 2026-10-02 00:35:27 +08:00
docs(coding-agent): document strict theme validation
This commit is contained in:
@@ -4,7 +4,7 @@
|
||||
|
||||
### Breaking Changes
|
||||
|
||||
- Moved the published theme JSON Schema to `schemas/theme.schema.json`. Update existing theme `$schema` references to the new path.
|
||||
- Moved the published theme JSON Schema to `schemas/theme.schema.json` and made theme loading reject unknown top-level properties and unknown properties under `colors` or `export`. Update existing theme `$schema` references to the new path, define reusable custom colors under `vars`, and remove unsupported metadata.
|
||||
|
||||
### Changed
|
||||
|
||||
|
||||
@@ -163,7 +163,7 @@ vim ~/.pi/agent/themes/my-theme.json
|
||||
- `vars` is optional. Define reusable colors here, then reference them in `colors`.
|
||||
- `colors` must define all 53 required tokens. `thinkingMax` and the two search highlight tokens are optional and use the fallbacks listed below.
|
||||
|
||||
The `$schema` field enables editor auto-completion and validation.
|
||||
The `$schema` field enables editor auto-completion and validation. Theme objects are strict: only documented top-level fields and color tokens are accepted. Define reusable custom colors under `vars`; custom keys under `colors` or `export` and additional top-level metadata are rejected.
|
||||
|
||||
## Color Tokens
|
||||
|
||||
|
||||
Reference in New Issue
Block a user