|
| 1 | +--- |
| 2 | +'@object-ui/types': minor |
| 3 | +--- |
| 4 | + |
| 5 | +**BREAKING (shipped as `minor` — see below):** thirteen node types now refuse |
| 6 | +both content channels by name. Each one's renderer reads neither `body` nor |
| 7 | +`children`, so an authored child list on it rendered nothing, with no |
| 8 | +render-time error or warning and no element; only the parser tier's |
| 9 | +`not-a-container` warning (objectui#9910) noticed it (objectui#9256). |
| 10 | + |
| 11 | +- `markdown`, `chart`, `bar-chart`, `code-editor`, `detail`, `report`: both keys |
| 12 | + are now `?: never` on the TypeScript face (`MarkdownSchema`, `ChartSchema`, |
| 13 | + `BarChartSchema`, `CodeEditorSchema`, `DetailSchema`, |
| 14 | + `ReportComponentSchema`) and a by-name refusal on the zod mirror, each kept a |
| 15 | + member of the mirror shape. |
| 16 | +- `list-view`: a by-name refusal on the zod mirror. `ListViewSchema`'s |
| 17 | + TypeScript face is derived from that mirror, so it refuses both keys too. |
| 18 | +- `page-designer`, `data-model-designer`, `process-designer`, |
| 19 | + `report-designer`, `object-manager`, `field-designer`: `?: never` on the |
| 20 | + TypeScript face (`PageDesignerSchema`, `DataModelDesignerSchema`, |
| 21 | + `ProcessDesignerSchema`, `ReportDesignerSchema`, `ObjectManagerSchema`, |
| 22 | + `FieldDesignerSchema`). None of them has a zod mirror, so the TypeScript face |
| 23 | + is the only one that changes. |
| 24 | + |
| 25 | +What moves for an author: |
| 26 | + |
| 27 | +- `children` on any of these nodes type-checked, and parsed green where a zod |
| 28 | + mirror exists; it is now refused at authoring time and, where a zod mirror |
| 29 | + exists, at `safeParse` time, at its own path. |
| 30 | +- `body` was already refused on these faces, by `BaseSchema`. On the zod |
| 31 | + mirrors its refusal message now names what the node renders instead, where |
| 32 | + it used to point at `children`, which these nodes do not read either. |
| 33 | + |
| 34 | +No render behaviour changes: nothing read these keys, which is the whole reason |
| 35 | +they could be refused. |
| 36 | + |
| 37 | +Migration: each of these nodes renders from its own keys, so there is no channel |
| 38 | +to move the content to. Put it in the key the node does render (`markdown`'s |
| 39 | +`content`, a `detail` tab's `content`, a chart's `data`), place it beside the |
| 40 | +node in a container that reads `children`, or drop it. |
| 41 | + |
| 42 | +`minor` rather than `major` because this repo's version policy forbids `major` |
| 43 | +in any changeset — one `fixed` group — and records `minor` plus an explicit |
| 44 | +breaking note as the spelling for a breaking change here. |
0 commit comments