fix(examples): catalog entries author the keys their renderers read (#4624)

[yinlianghui]

Fixes #4624
Fixes #4626
Fixes #4625

Three catalog-authoring defects on one surface, plus the #4616 render pin's exclusion tables shrinking to match reality. Authoring-side only: no renderer or package source is touched.

One of the three filings turned out to be partly mis-diagnosed. That is reported below rather than papered over, and the pin's header is corrected to match what was measured.

Piece 1 — #4624, components-disclosure-toggle-group/with-labels

Named root type "single", which nothing registers. Now "toggle-group" + "selectionType": "single", the spelling both siblings already use. The items keep their icon keys: ToggleGroupItem.icon is a declared field (packages/types/src/disclosure.ts:131), so this is not the entry inventing a key — though no renderer reads it, filed as #4632.

This was the last unintentional OBJUI-001 tile in the corpus.

Piece 2 — #4626, the two "blank tile" entries

components-overlay-tooltip/basic-tooltip — filing confirmed. It authored its trigger under children. Renderer prop reads, packages/components/src/renderers/overlay/tooltip.tsx:

• line 28 renderChildren(schema.trigger) inside TooltipTrigger asChild
• line 31 (schema.content || renderChildren(schema.body)) inside TooltipContent

children is read nowhere, so the tile drew nothing at all. Measured as authored: 2 elements (both harness wrappers), empty text. Now authors trigger; measured after: 3 elements, text "Hover me".

components-overlay-hover-card/basic-hover-card — filing falsified on both of its claims. The issue states the text renderer reads content and that value is therefore never read. It reads both:

• packages/components/src/renderers/basic/text.tsx:35 and :40 both evaluate schema.content || schema.value

So the authored value WAS read, and the tile was not blank: measured as authored, it drew the text node "Hover over me". The pin's own non-vacuity control accepts text as well as elements (deliberately — components-basic-text/* are bare text nodes), so removing this entry's exclusion turns nothing red. That was verified by removing the exclusion BEFORE touching the entry: the run went red on 9 cases and this was not one of them.

What the entry did have is a different defect, one the filing did not name: a bare text node is not an element, so HoverCardTrigger asChild had nothing to clone and the card could never open. Measured contrast, same harness — a text trigger carrying a className renders a span that Radix wires (data-state="closed"), while the bare one renders no element at all. The trigger is now a link-variant button, which is the shape the renderer's own defaultProps declare for this slot (hover-card.tsx:50). The content slot keeps value, which is the key TextSchema declares (packages/types/src/layout.ts:56).

Note the deliberate non-change: the ruled correction value to content is a no-op at render time AND would author a key TextSchema does not declare. content appears only in the registry meta. That three-way disagreement is the real class question and is filed as #4631.

Piece 3 — #4625, the six components-form-calendar entries

Verify-first, as ruled. ui:calendar IS addressable as a schema type. Measured, not inferred:

• Registry.get(type) with no namespace argument looks the string up verbatim (packages/core/src/registry/Registry.ts:350-358), and register() stores the namespaced form under exactly ui:calendar (line 163). SchemaRenderer passes the authored type straight in: ComponentRegistry.get(evaluatedSchema.type) at packages/react/src/SchemaRenderer.tsx:506.
• Probe-rendered through this pin's own harness, before any entry was edited: { "type": "ui:calendar", "mode": "single" } produced 115 elements and painted the date-picker grid ("August 2026 SuMoTuWeThFrSa..."). The bare calendar keyword in the same probe produced 5 elements and "Error: DataSource required for object/api providers".

So all six now author ui:calendar and reach the form-calendar primitive the category exists to demo. form-integration is a div whose nested child was the offending node; only that child changed.

The bare keyword still resolves to plugin-calendar's ObjectCalendar. That is skipFallback: true working as designed, not something this PR routes around.

Piece 4 — the pin

examples/schema-catalog/test/catalog-gallery-render.test.tsx:

• All three entry exclusions removed (Docs gallery: components-disclosure-toggle-group/with-labels names root type "single", which no package registers #4624's, and Docs gallery: the basic-tooltip and basic-hover-card entries render a completely blank tile — each authors a key its renderer never reads #4626's two). Those entries now carry the full assertion set.
• The KNOWN_DIAGNOSTIC table is deleted entirely — it held only Docs gallery: the six components-form-calendar entries author the bare "calendar" keyword, which belongs to plugin-calendar's ObjectCalendar #4625's six DATASOURCE_REQUIRED exemptions. With no exemptions left, diagnosticsFor() is gone too and all three diagnostics are asserted for every non-excluded entry. Strictly stronger, and DATASOURCE_REQUIRED stays asserted as the regression guard that catches an entry sliding back to the bare keyword.
• Header prose corrected where this run falsified it, including the claim that the non-vacuity control "found Docs gallery: the basic-tooltip and basic-hover-card entries render a completely blank tile — each authors a key its renderer never reads #4626's two blank tiles" — it found one.

Untouched, as ruled: the deliberate OBJUI-001 demo entry, the three Monaco and three maplibre environment abstentions, and AUTHORED_TEXT_EXEMPT (#4627).

Red-first, then green

Predictions were written before the run. Pin edits made first, entries untouched, so the red is the pin reporting on the real corpus:

× components-disclosure-toggle-group/with-labels renders without a red tile 11ms
× components-form-calendar/custom-style renders without a red tile 12ms
× components-form-calendar/date-range renders without a red tile 6ms
× components-form-calendar/form-integration renders without a red tile 7ms
× components-form-calendar/multiple-dates renders without a red tile 6ms
× components-form-calendar/simple-calendar renders without a red tile 6ms
× components-form-calendar/single-date renders without a red tile 6ms
× components-overlay-tooltip/basic-tooltip renders without a red tile 1010ms
× the whole corpus produces zero unknown-type panels and zero error tiles 3003ms

Tests  9 failed | 431 passed (440)

Verbatim diagnostics:

AssertionError: components-disclosure-toggle-group/with-labels shows "Unknown component type":
expected 'Unknown component type: single...' not to contain 'Unknown component type'
+ Unknown component type: single (OBJUI-001)

AssertionError: components-form-calendar/custom-style shows "DataSource required for object/api providers":
Received: "Error: DataSource required for object/api providers"

AssertionError: components-form-calendar/form-integration ...
Received: "Select a dateError: DataSource required for object/api providers"

basic-tooltip and the corpus case fail differently — on the non-vacuity control inside renderEntry, expected true, received false at the drewSomething waitFor — because a tile that draws nothing never settles. That is the blank-tile signature, and it is the one #4626 half that reproduced.

components-overlay-hover-card/basic-hover-card is absent from that list: it passes with its exclusion removed and no entry change. Predicted red, measured green — reported rather than forced.

After the entry re-authoring, same command:

Test Files  1 passed (1)
     Tests  440 passed (440)

440 vs the 437 of the pre-change baseline: three entries left the exclusion table and became asserted cases.

Reverse verification. Fix taken back out with git checkout origin/main -- ... (never git stash), pin left in place: the same 9 cases fail, basic-hover-card again absent. Restored with git checkout HEAD -- ... and all nine files verified bit-identical by sha256sum -c.

Verification

pnpm exec vitest run --maxWorkers=2 scripts/ examples/schema-catalog
  Test Files  50 passed (50)
       Tests  2531 passed (2531)

pnpm --filter '@object-ui/example-schema-catalog^...' build   (build closure first)
pnpm --filter @object-ui/example-schema-catalog type-check     (clean)
pnpm --filter @object-ui/example-schema-catalog lint           (0 errors; 2 pre-existing warnings in untouched files)

Gate battery, all PASS: check-control-bytes, check-phantom-dependencies, check-changeset-presence, check-changeset-no-major, check-changeset-fixed, check-type-check-coverage, check-lint-coverage, check-doc-links. Control-byte self-scan over the changed files (and untracked: none) is clean.

Changeset

None owed, and skip-changeset is applied instead: @object-ui/example-* is in .changeset/config.json's ignore list and @object-ui/example-schema-catalog is "private": true. The diff is entirely under examples/schema-catalog/**. check-changeset-presence passes.

Out of scope, filed rather than fixed here

• A component type has THREE declared surfaces that disagree (TS schema type / registry meta inputs / renderer prop reads), and nothing reconciles or enforces them #4631 — a component type has three declared surfaces (TS interface / registry meta inputs / renderer reads) that disagree. This is Docs gallery: the basic-tooltip and basic-hover-card entries render a completely blank tile — each authors a key its renderer never reads #4626's class question, re-filed standalone with the tooltip and text specimens measured above. TooltipSchema declaring a required children that the renderer ignores means an author following the published type gets a blank tile.
• finding(components): ToggleGroupItem.icon is declared in types but no renderer reads it — authored icons render nothing #4632 — ToggleGroupItem.icon is declared but no renderer reads it (observation-class).
• examples/schema-catalog pnpm regenerate is destructive: it blanks six plugin-dashboard entries' curated titles and descriptions #4633 — pnpm --filter @object-ui/example-schema-catalog regenerate is destructive on current main: it blanks six plugin-dashboard entries' curated titles and descriptions. NOT run for this PR and not needed (no entry added, removed or renamed; index.ts only imports the JSON by path), so index.ts is unchanged here.

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
objectui	Ignored		Aug 14, 2026 3:50am