Uh oh!
There was an error while loading. Please reload this page.
feat(spec): source the react-tier component contract from the spec schemas - #2478
Merged
Conversation
…hemas Per the platform-author steer: the standard components are already defined in the spec (FormView/ListView in view.zod, RecordDetails/Highlights/RelatedList/Path in component.zod, Chart in chart.zod) — so generate the AI contract FROM them instead of hand-authoring. - packages/spec/src/ui/react-blocks.ts — the component-type -> spec-schema index (the 'completion' that lets tooling enumerate a block's schema) + a thin React-interaction overlay (binding/controlled/callback — objectName, recordId, mode, onSuccess, onRowClick, …, which are inherently React and absent from the declarative schema). Curated via per-block dataProps allowlists (ADR-0080). - scripts/build-react-blocks-contract.ts — generator: z.toJSONSchema(spec schema) -> data props (authoritative, with the spec's own descriptions); merge overlay; emit the AI reference (.md) + machine contract (.json). - Replaces the Phase-1 hand-authored contract (drift-free, spec-sourced now). - api-surface snapshot updated (+4 additive exports, 0 breaking). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
📓 Docs Drift CheckThis PR changes 1 package(s): 90 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| fs.writeFileSync(OUT_JSON, JSON.stringify(contract, null, 2) + '\n'); | ||
| // markdown | ||
| const esc = (s: string) => String(s).replace(/\|/g, '\\|'); |
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Jun 30, 2026
os-zhuang added a commit
that referenced
this pull request
Jun 30, 2026
Records the model that the spec↔contract↔conformance↔prop-gate work converged on (now implemented + merged across framework #2478/#2480/#2482/#2484/#2485/#2488/ #2489 and objectui #2113/#2115), so future contributors don't re-litigate it: - the spec zod schema is the protocol source of truth; the AI-facing contract is GENERATED from it (zero-drift), never hand-authored; - registry inputs are the designer palette (a curated subset) — spec-only is a soft signal, frontend-only is the actionable one; - React-interaction props (callbacks/controlled/binding escape-hatches) live in a thin overlay, not the spec; declaring a genuine binding there is how a frontend-only prop is closed (baseline now 0 frontend-only); - conformance is a build-time baseline ratchet (build-console.sh, warn-only), not a per-PR gate — the manifest only exists at console-build time; - authoring correctness is a hard gate at os validate (missing-required = error, typo = warning); and the dogfood golden page proves the chain closes. Captures the alternatives rejected (copy props into spec / per-PR hard gate / hand-authored contract / registry-as-source). Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Course-correction from the platform-author steer: the standard components are already defined in the spec (FormView/ListView in
view.zod, RecordDetails/Highlights/RelatedList/Path incomponent.zod, Chart inchart.zod) — so the AI contract is now generated from them, not hand-authored.packages/spec/src/ui/react-blocks.ts— the component-type → spec-schema index (the small 'completion' that lets tooling enumerate which schema defines a block) + a thin React-interaction overlay (binding/controlled/callback— objectName, recordId, mode, onSuccess, onRowClick, … — inherently React, absent from the declarative schema). Curated per-block viadataPropsallowlists (ADR-0080 'capability ≠ contract').scripts/build-react-blocks-contract.ts— generator:z.toJSONSchema(spec schema)→dataprops with the spec's own descriptions; merge the overlay; emit the AI reference (references/react-blocks.md) + machine contract (.json).pnpm --filter @objectstack/spec gen:react-blocks.The result:
<ObjectForm>/<ListView>/<RecordDetails>/… each list their props with the spec's authoritative descriptions for config props + the React overlay for interaction. Follow-up:os buildprop-validation gate consuming this contract.🤖 Generated with Claude Code