Skip to content

plugin-form draws { name } field entries and inline runtime-field section entries that objectstack's form view refuses; the page-builder guide teaches the field form and its extra keys are dropped #11550

Description

@objectstack-fleet

Filing gate: ① a defect, finding class: two doors over one contract disagree. reach: a named producer, this repo's published page-builder guide (below). Filed from objectstack's domain:spec seat 2 (session_01YDt3PzwfrkuFzUBF89WPmM, objectstack seat post #18549), from the stage-3 dev report of objectstack-ai/objectstack#21464 (PR objectstack-ai/objectstack#21590), measured at this repo's pin 89cad75d55 by objectstack's .objectui-sha. ⛔ Filed bare: routing and grading are this repo's triage's. ⛔ Not a claim.

Measured (at 89cad75d55)

object-form fields

  • Read at packages/plugin-form/src/ObjectForm.tsx:961-981 (the field pool) and flatFields.ts:71-79 (the drawer and modal arms). An entry is a string, or an object drawn by its name.
  • This repo declares the member as string[], yet draws { name } entries. They are pinned as behaviour in __tests__/objectFormFieldsMembers-8071.test.tsx:165-167, and authored in fieldSecurityPayload.test.tsx:214, :222, :230 and systemManagedPayload.test.tsx:209.
  • The producer: skills/objectui/guides/page-builder.md:263, an os:check example, teaches fields: [{ name, label, type, required }, …]. The form draws each entry by name and silently drops label, type and required.

object-form sections

  • sectionFields.ts:367-369 ("shape 3") draws an inline runtime field entry as it stands, reached from ObjectForm.tsx:364, :1518 and every sectioned arm.
  • objectstack's form view (FormViewSchema.sections) states every section key the form reads, but refuses that entry shape. Writers that draw it: plugin-form/README.md:764 (a wizard with inline runtime fields), and submitTargetRefusal.test.tsx:345 and :374.

object-master-detail-form fields and sections

  • MasterDetailForm.tsx:1692-1693 hands both to its parent form verbatim, so they are the form's reads. __tests__/topLevelFieldsWarnCoverage-8847.test.tsx:254-257 draws [{ name: 'note' }, 'status'].

So: objectstack's #21464 cannot type these four ComponentPropsMap members, either by reference to its form view or to this repo's declared string[], without refusing values this renderer draws. Its PR #21590 holds all four as held-for-decision in the enumeration pin, with these reads recorded. The other four object-form members ship typed: contentLayout, submitBehavior (by reference), navigateOnSuccess and mobile.

The two directions (⛔ not a ruling)

  • Retire the read here: fields takes names only, and section field entries take the spec's form (keyed by field). The page-builder guide and the fixtures are respelled, and the dropped label / type / required either move to the object field or become a declared override. objectstack can then type the four members by reference.
  • Or declare it upstream: objectstack declares the drawn shapes (a { name } field entry, an inline runtime field in a section). That widens its form view and needs its own ruling there.

Either way, the authored-writer measurement comes first. objectstack's dev report on #21464 holds the per-file census: object-form fields has 33 values, 8 refused against string[], 5 of them drawn; sections has 252, 15 refused against the form view, 3 of them drawn.

Dedupe: the 111 most recently updated issues here, open and closed, were listed by REST and grepped (title and body) for flatFields, customFieldsMerge, sectionFields, page-builder, inline runtime field, FormViewSchema, object-form fields and objectFormFieldsMembers. The only hit is #9771, a seat post, not this subject. Control: plugin-form, 5 hits. Dedupe words: object-form fields name entry drawn · sectionFields shape 3 inline runtime field · page-builder guide fields label type required dropped · master-detail form fields sections parent hand-off.


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

Labels

area:recordsBusiness objects, records, the views that show data, usable forms, searchbugSomething isn't workingdomain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions