feat(spec)!: FlowSchema refuses a flow whose top-level nodes[] declares the same id twice (#15713)
#21764
pr-automation.yml
on: pull_request
Check PR Size
0s
Check Changeset
55s
Auto Label
0s
Annotations
1 notice
|
Check Changeset:
.changeset/flow-node-id-uniqueness.md#L0
ADR-0087 exemption (no-migration-prescription): No authorable key is renamed, retired or re-typed: `nodes[].id` keeps its name, its type and its describe, and every flow whose top-level node ids are unique parses byte-identically. The only newly refused shape is two top-level nodes sharing one id — a collision, not a spelling — and its remedy is to rename one of the two (and re-point the edges that meant it), which is authoring intent no `objectstack migrate meta` rewrite can choose for the author. The census over this repo at `1f2a02ba` (997 literal `nodes[]` arrays, 2,186 nodes, 2,011 literal ids under `packages/**` and `examples/**` including tests; 79 arrays / 256 nodes excluding tests; AST scan with a planted-duplicate control that reads 1) found zero instances, so there is no in-repo file to name.
|