Skip to content

Document default field-schema validation (rule 24b)#45

Merged
yavorpanayotov merged 1 commit into
mainfrom
docs/default-field-validation
Jun 16, 2026
Merged

Document default field-schema validation (rule 24b)#45
yavorpanayotov merged 1 commit into
mainfrom
docs/default-field-validation

Conversation

@yavorpanayotov

Copy link
Copy Markdown
Collaborator

Documents the default-literal field validation actioned in juxt/allium-tools#46 (the Gap B drift-detection follow-up from #43).

Adds rule 24b: every field in a default object literal must be a field declared on the named entity/value type, recursing into nested object literals — so renaming or removing a field surfaces as a drift error at check time. Complements existing 24a (qualified-type schema resolution) and 14c (empty-list element type, also now enforced).

Refs #43

🤖 Generated with Claude Code

Adds validation rule 24b: every field in a `default` object literal must be
declared on the named entity/value type, recursing into nested object literals,
so field renames/removals surface as drift errors at check time. Complements the
existing 24a (qualified-type schema resolution) and 14c (empty-list element
type). Implemented in juxt/allium-tools#46.

Refs #43

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@yavorpanayotov yavorpanayotov merged commit 2b7d66f into main Jun 16, 2026
1 check passed
@yavorpanayotov yavorpanayotov deleted the docs/default-field-validation branch June 16, 2026 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant