Skip to content

docs(changeset): the manifest serializer forwards seven keys per input, not six #10318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
objectstack-fleet merged 2 commits into from
Sep 24, 2026
Merged

docs(changeset): the manifest serializer forwards seven keys per input, not six #10318

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b2df78a
docs(changeset): the manifest serializer forwards seven keys per inpu…
claude Sep 24, 2026
6f1275f
Merge remote-tracking branch 'origin/main' into HEAD
claude Sep 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .changeset/5905-componentinput-inputtype-tombstone.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ over the same regions, so the instrument was not blind. The other 192 in-repo `i
hits are a DIFFERENT face: `FormField.inputType` (`zod/form.zod.ts`), the text-input
renderer's prop, and `SchemaBuilder.inputType`, none of which sit on a `ComponentInput`.
The publication path is unchanged and was re-confirmed: `packages/sdui-parser/src/index.ts`
forwards exactly six keys per input — `name`, `type`, `required`, `enum`, `binding`,
forwards exactly seven keys per input — `name`, `type`, `of`, `required`, `enum`, `binding`,
`description` — so an authored `inputType` could not reach the published
`sdui.manifest.json` even in principle.

Expand Down
4 changes: 2 additions & 2 deletions .changeset/5905-componentinput-retire-constraint-keys.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ Retire `ComponentInput`'s four inert constraint keys — `min`, `max`, `step` an

All four were declared on `ComponentInput` and read by nothing, on either path. No consumer
reads them off a `ComponentInput` value, and the manifest serializer
(`packages/sdui-parser/src/index.ts`) forwards exactly six keys per input — `name`, `type`,
`required`, `enum`, `binding`, `description` — so a value authored here could not reach the
(`packages/sdui-parser/src/index.ts`) forwards exactly seven keys per input — `name`, `type`,
`of`, `required`, `enum`, `binding`, `description` — so a value authored here could not reach the
published `sdui.manifest.json` even in principle. Re-measured on this branch's merge-base
rather than inherited from the card: a structural census over every `inputs:` array in the
repository (219 regions, all tracked files) scores `min` **0**, `max` **0**, `step` **0**
Expand Down
4 changes: 2 additions & 2 deletions .changeset/7493-componentinput-retire-label-defaultvalue-advanced.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,8 @@ They are the three keys the manifest serializer does not forward, and nothing re
publication or consumption path.

No manifest ever published them, so no consumer could ever have read them. `sdui-parser`'s
serializer (`packages/sdui-parser/src/index.ts`) forwards exactly six keys per input — `name`,
`type`, `required`, `enum`, `binding`, `description` — so a value authored under any of the three
serializer (`packages/sdui-parser/src/index.ts`) forwards exactly seven keys per input — `name`,
`type`, `of`, `required`, `enum`, `binding`, `description` — so a value authored under any of the three
never reached `sdui.manifest.json`, the generated JSX `.d.ts`, or a diagnostic; its boundary type
has no slot for them; the registry's data-source seam reads `name` only; and neither the designer
nor the app-shell inspectors consult registry `inputs` at all. A structural census over every
Expand Down
Loading