|
| 1 | +--- |
| 2 | +'@object-ui/types': minor |
| 3 | +'@object-ui/core': patch |
| 4 | +'@object-ui/components': patch |
| 5 | +'@object-ui/layout': patch |
| 6 | +'@object-ui/app-shell': patch |
| 7 | +'@object-ui/plugin-ai': patch |
| 8 | +'@object-ui/plugin-calendar': patch |
| 9 | +'@object-ui/plugin-charts': patch |
| 10 | +'@object-ui/plugin-chatbot': patch |
| 11 | +'@object-ui/plugin-dashboard': patch |
| 12 | +'@object-ui/plugin-designer': patch |
| 13 | +'@object-ui/plugin-detail': patch |
| 14 | +'@object-ui/plugin-editor': patch |
| 15 | +'@object-ui/plugin-form': patch |
| 16 | +'@object-ui/plugin-gantt': patch |
| 17 | +'@object-ui/plugin-grid': patch |
| 18 | +'@object-ui/plugin-kanban': patch |
| 19 | +'@object-ui/plugin-list': patch |
| 20 | +'@object-ui/plugin-map': patch |
| 21 | +'@object-ui/plugin-markdown': patch |
| 22 | +'@object-ui/plugin-report': patch |
| 23 | +'@object-ui/plugin-timeline': patch |
| 24 | +'@object-ui/plugin-tree': patch |
| 25 | +'@object-ui/plugin-view': patch |
| 26 | +--- |
| 27 | + |
| 28 | +**Breaking for authored metadata:** `ComponentInput.label`, `ComponentInput.defaultValue` and |
| 29 | +`ComponentInput.advanced` are RETIRED on both faces (objectui#7493 item ① and objectui#7781; |
| 30 | +maintainer ruling A of 2026-09-06, immediate, no deprecation window; ADR-0049 enforce-or-remove). |
| 31 | +They are the three keys the manifest serializer does not forward, and nothing read them on any |
| 32 | +publication or consumption path. |
| 33 | + |
| 34 | +No manifest ever published them, so no consumer could ever have read them. `sdui-parser`'s |
| 35 | +serializer (`packages/sdui-parser/src/index.ts`) forwards exactly six keys per input — `name`, |
| 36 | +`type`, `required`, `enum`, `binding`, `description` — so a value authored under any of the three |
| 37 | +never reached `sdui.manifest.json`, the generated JSX `.d.ts`, or a diagnostic; its boundary type |
| 38 | +has no slot for them; the registry's data-source seam reads `name` only; and neither the designer |
| 39 | +nor the app-shell inspectors consult registry `inputs` at all. A structural census over every |
| 40 | +`inputs:` array in the repository (re-measured on this change's merge-base, `name` 951 and `type` |
| 41 | +951 as the controls) counted the writes: `label` 908, `defaultValue` 245, `advanced` 9 — written on |
| 42 | +nearly every registration, read by nothing. |
| 43 | + |
| 44 | +FROM → TO, per key — all three **TOMBSTONED, not removed**, because the route was measured on |
| 45 | +the built face before it was chosen: `ComponentInputSchema` is a non-strict `z.object`, and an |
| 46 | +undeclared key parses GREEN and is silently STRIPPED, so a deletion would have swallowed 1,162 |
| 47 | +authored values in silence. The tombstone is what makes the refusal loud and by name. |
| 48 | + |
| 49 | +- `label?: string` → `label?: never` on the interface, `retirementTombstone()` on the Zod mirror. |
| 50 | + Migration: delete the key. An input is identified by its `name` on every path that reaches it; |
| 51 | + nothing ever rendered a label for it. |
| 52 | +- `defaultValue?: any` → `defaultValue?: never` / `retirementTombstone()`. Migration: delete the |
| 53 | + key. The renderer's own fallback read IS the default; tell the author about it in `description`, |
| 54 | + which IS published. (Tightening the type to `unknown` was ruled out: it closes no error class, |
| 55 | + since nothing reads the value.) |
| 56 | +- `advanced?: boolean` → `advanced?: never` / `retirementTombstone()`. Migration: delete the key. |
| 57 | + No designer surface ever hid an "advanced" input; there is nothing to write instead. |
| 58 | + |
| 59 | +The retirement kit: `?: never` on `ComponentInput` (`packages/types/src/base.ts`), so authoring one |
| 60 | +is a `tsc` error at the registration site; `retirementTombstone()` on `ComponentInputSchema` |
| 61 | +(`packages/types/src/zod/base.zod.ts`), so an authored value is REFUSED at parse time with |
| 62 | +`code: 'invalid_type'`, the key named in the issue `path`, and the migration note as the message |
| 63 | +(one string, both channels). Pinned in |
| 64 | +`packages/types/src/__tests__/component-input-retired-keys-7493.test.ts`, which also holds a |
| 65 | +tree-scoped absence census over every `inputs:` array under `packages/**` and `apps/**`. |
| 66 | + |
| 67 | +Accept-set change, stated plainly for reviewers: a document that sets any of the three keys on a |
| 68 | +`ComponentInput` used to parse GREEN (the value was then dropped by the serializer) and now parses |
| 69 | +RED. Every in-repo authoring site — 1,199 keys across 110 registration files, the three standalone |
| 70 | +`ComponentInput[]` arrays and the two named input arrays `tsc` found included — is deleted in the same change, as the ruling's split rule |
| 71 | +requires; the `WidgetRegistry` seam no longer copies the widget-manifest values onto the synthesized |
| 72 | +`ComponentInput` (they fed nothing), and the data-source declaration `ELEMENT_DATA_SOURCE_INPUT` |
| 73 | +drops its `label`. The patch entries on the other packages record exactly that: their registrations |
| 74 | +stop authoring inert keys, with no runtime or published-manifest change. |
| 75 | + |
| 76 | +The nine test files that read `defaultValue` off a registration were re-pinned against the |
| 77 | +renderer's ACTUAL default (its own fallback read, or the `defaultProps` it ships) instead of the |
| 78 | +declaration that went away; two assertions that only restated the shadow default were dropped with |
| 79 | +the reason on the line. |
| 80 | + |
| 81 | +The in-repo zero is what was measured. Whether anything OUTSIDE this repository writes these keys |
| 82 | +is not measurable from here (the objectui#5674 limit); converting such a write from a silent drop |
| 83 | +into a named refusal is exactly what the tombstones buy. `WidgetInput`'s own `label` / |
| 84 | +`defaultValue` / `advanced` (the widget-manifest face) stay declared and writable — nothing has |
| 85 | +ruled on that face; that it now has no reader either is recorded as objectui#7911. |
0 commit comments