Observation-class finding, filed from objectui#7006 (the same defect on content/docs/guide/react-pages.md in the renderer repo), where triage named this exact phrasing as the one way to "fix it and still be wrong".
(Tag names below are written without angle brackets — the body sanitizer eats short angle-bracket fragments.)
What the page says
content/docs/ui/react-pages.mdx:34-35, the paragraph #13734 added to close #12650:
Those tags are the registered type names, written verbatim — lowercase and
kebab-case, keeping the namespace prefix where a block has one: list-view,
object-form, object-chart, record:related_list, flex.
The lead clause ("registered type names, written verbatim") is exactly right. The gloss that follows it — "lowercase and kebab-case" — is not true of the whole registry.
Measured
packages/core/src/registry/public-blocks.ts in objectstack-ai/objectui (b8e3f8379) holds 57 entries. 28 carry a namespace prefix (record: / page: / element: / action:), and 4 are snake_case after the colon:
record:related_listrecord:line_itemsrecord:quick_actionsrecord:reference_rail
The whitelist is new Set(Object.keys(manifest.components)) (packages/sdui-parser/src/index.ts:41) compared by exact Set.has (packages/sdui-parser/src/parse.ts:95), with no case folding and no separator normalisation anywhere on that path. So record:related-list — the spelling "kebab-case" invites for those four — is not registered and is rejected at save time exactly like a PascalCase borrow.
Why it is only a finding, not a defect that bites today
The paragraph's own example list includes record:related_list, so an author reading the examples sees the underscore and is contradicted in place. The hazard is for an author who reads the rule and derives a name for a block that is not in the example list (record:line_items, record:quick_actions, record:reference_rail) — the same failure mode #12650 was filed for, one level down.
Suggested shape
Drop the "lowercase and kebab-case" gloss and let the verbatim rule stand on its own, adding a snake_case example so the shape is demonstrated rather than described. objectui#7939 words it that way for the renderer repo's copy of this page:
Those tags are the registered type names, written verbatim — whatever the registry spells, character for character, including a record: / page: / element: / action: namespace prefix and any underscore inside the name … and neither is a name re-spelled to look uniform — record:related-list is not registered, only record:related_list is.
Provenance
Found while implementing objectui#7006 (the sister-repo instance of #12650), whose triage weighted this wording trap explicitly. Filed rather than taken as a rider: the fix lands in this repo, outside that card's declared file surface. Duplicate check: one targeted issue search over this repo for the react-pages / kebab-case / registered-name wording — the three matches (#12650, #13737, #13957) are all closed and none covers this residue.
Observation-class finding, filed from objectui#7006 (the same defect on
content/docs/guide/react-pages.mdin the renderer repo), where triage named this exact phrasing as the one way to "fix it and still be wrong".(Tag names below are written without angle brackets — the body sanitizer eats short angle-bracket fragments.)
What the page says
content/docs/ui/react-pages.mdx:34-35, the paragraph #13734 added to close #12650:The lead clause ("registered type names, written verbatim") is exactly right. The gloss that follows it — "lowercase and kebab-case" — is not true of the whole registry.
Measured
packages/core/src/registry/public-blocks.tsin objectstack-ai/objectui (b8e3f8379) holds 57 entries. 28 carry a namespace prefix (record:/page:/element:/action:), and 4 are snake_case after the colon:record:related_listrecord:line_itemsrecord:quick_actionsrecord:reference_railThe whitelist is
new Set(Object.keys(manifest.components))(packages/sdui-parser/src/index.ts:41) compared by exactSet.has(packages/sdui-parser/src/parse.ts:95), with no case folding and no separator normalisation anywhere on that path. Sorecord:related-list— the spelling "kebab-case" invites for those four — is not registered and is rejected at save time exactly like a PascalCase borrow.Why it is only a finding, not a defect that bites today
The paragraph's own example list includes
record:related_list, so an author reading the examples sees the underscore and is contradicted in place. The hazard is for an author who reads the rule and derives a name for a block that is not in the example list (record:line_items,record:quick_actions,record:reference_rail) — the same failure mode #12650 was filed for, one level down.Suggested shape
Drop the "lowercase and kebab-case" gloss and let the verbatim rule stand on its own, adding a snake_case example so the shape is demonstrated rather than described. objectui#7939 words it that way for the renderer repo's copy of this page:
Provenance
Found while implementing objectui#7006 (the sister-repo instance of #12650), whose triage weighted this wording trap explicitly. Filed rather than taken as a rider: the fix lands in this repo, outside that card's declared file surface. Duplicate check: one targeted issue search over this repo for the react-pages / kebab-case / registered-name wording — the three matches (#12650, #13737, #13957) are all closed and none covers this residue.