From 6ce28b777773fe401c4eeb1f0d62065fb91821e7 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 3 Oct 2026 15:04:43 +0000 Subject: [PATCH] docs(skills): the page-builder guide's object-form example names its fields; a per-form override goes on a section entry (objectui#11550) Executes item 1 of triage ruling 5969880008 on the governed half. The `os:check` `object-form` example taught `fields: [{ name, label, type, required }, ...]`; the form draws each entry by name and drops the other three keys, and the declared member is `string[]`. It now reads `"fields": ["name", "email"]`. The note above it, which paired grid `field` with form `name`, now says where labels, types and `required` come from (the object fields) and where a per-form override goes (a `sections[].fields` entry). Net -3 lines. Claude-Session: https://claude.ai/code/session_01FjqrwXPfSMkSfkKYDSRkN2 Co-authored-by: Claude --- skills/objectui/guides/page-builder.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/skills/objectui/guides/page-builder.md b/skills/objectui/guides/page-builder.md index 5fdc817ae5..d2b1d07709 100644 --- a/skills/objectui/guides/page-builder.md +++ b/skills/objectui/guides/page-builder.md @@ -251,11 +251,11 @@ When pages need heavy widgets (grids, forms, kanbans, charts), import the plugin } ``` -> **Grid columns key off `field`; form fields key off `name`.** The two layers sit -> next to each other here and use the same pair of words for opposite things: -> `ListColumn.field` names the object field a column shows, while `FormField.name` -> names the field a form input writes. A grid column written as `{ "name": ... }` -> names no field, so `ObjectGrid` drops it. +> **Grid columns are `{ "field" }` objects; `object-form` `fields` are names.** +> `ListColumn.field` names the object field a column shows, so a grid column +> written as `{ "name": ... }` names no field and `ObjectGrid` drops it. Form +> labels, types and `required` come from the object fields; a per-form override +> goes on a `sections[].fields` entry, `{ "field": "email", "required": true }`. **Form plugin example:** @@ -265,10 +265,7 @@ When pages need heavy widgets (grids, forms, kanbans, charts), import the plugin "properties": { "objectName": "customer", "mode": "edit", - "fields": [ - { "name": "name", "label": "Name", "type": "text", "required": true }, - { "name": "email", "label": "Email", "type": "text" } - ] + "fields": ["name", "email"] } } ```