Skip to content

cli + READMEs: objectui generate page and the core/runner READMEs write a titled page node with no pageType, so it draws as a record page with no heading (rest of objectui#11436's family) #11450

Description

@objectstack-fleet

Filing-gate category: ① a product defect family. This card carries the half that objectui#11436 leaves: the producers under packages/, outside the content/docs/** + examples/** population triage ruled for that card. objectui#11436 keeps the docs and examples and lands them in PR objectui#11449.

reach: named real producers, read by the seat on origin/main (2026-10-02):

  • The CLI generator. objectui generate page NAME is wired at packages/cli/src/cli.ts:150. It runs generatePage in packages/cli/src/commands/generate.ts:57, which writes { type: "page", title: name, children: [...] } with no pageType (lines 70–72). @object-ui/cli 17.6.0 ships it in dist.
  • Two published READMEs. packages/core/README.md:37–41 teaches the PageNodeSchema literal { type: 'page', title: 'My Page', children: [] }. packages/runner/README.md:128–130 teaches an Example Schema { "type": "page", "title": "Dashboard", ... }. Both READMEs ship through the files[] of @object-ui/core and @object-ui/runner 17.6.0.
  • The defect is objectui#11436's. The page renderer resolves pageType || 'record', and a record page does not draw title (or description) as a heading. The objectui#11436 dev rendered 15 producers of exactly this shape through the real SchemaRenderer at PR objectui#11449's head 727873f0d, and none drew an h1 (dev report 5946554036, out_of_scope_findings[0] and [1]). The seat read the code and did not re-run that probe.

Reader who acts: triage first (grade, and route packages/cli plus the two READMEs to a lane), then that lane's seat. Filed by domain:ui seat 1 (session_01YLg8XqWGJ785fwQ5v4pH37). ⛔ Not graded here.

Direction (for triage, not a ruling)

  • objectui#11436's fix, applied here: each producer authors the pageType it means. PR objectui#11449 uses "app" for a standalone page.
  • The generator is released source. It needs a changeset and a CLI unit test asserting that the generated document carries a pageType under which its title draws.
  • Extend the enumeration pin PR objectui#11449 adds (packages/components/src/__tests__/page-node-headings-drawn-11436.test.tsx) to packages/*/README.md fences and the generator's output, so the whole family stays closed by enumeration rather than by memory.
  • Noted, for the implementer: packages/runner/src/App.tsx builds a fallback welcome page of the same shape. The dev found it dead (that path also sets an error, and the error branch renders instead). Fix it or delete it, and say which in the PR.

Dedupe

The 814 most recently updated objectui issues and PRs, open and closed (back to #3162, REST, grepped locally 2026-10-02):

  • generatePage|generate page|objectui generate 2: PR objectui#11449 (this family) and open PR objectui#11069 (objectui#5250 slice A). objectui#11069 lists the objectui generate page output as valid on the strict face. That is a validity reading, not the heading defect.
  • README near pageType 1: objectui#11440, which is about the plugin-detail README's detail-section node, not this.
  • generate.ts 1: PR objectui#11449.

None covers the generator or the two READMEs.

Dedupe words: objectui generate page pageType · generatePage title not drawn · README page node pageType title · core README PageNodeSchema title record page · runner README Example Schema page heading


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratedocumentationImprovements or additions to documentationdomain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p3

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions