@praxisui/dynamic-form 9.0.4-rc.2 → 9.0.4-rc.21

package/docs/schema-driven-layout-materialization-rfc.md

@@ -4,7 +4,7 @@ doc_type: "rfc"
 component: "praxis-dynamic-form"
 status: "implemented-partial"
 owner: "praxis-ui"
-last_updated: "2026-06-29"
+last_updated: "2026-08-03"
 classification: "contrato-publico, arquitetural"
 ---
 
@@ -116,6 +116,16 @@ export interface DynamicFormDetailSummaryPolicy {
   widthPrecedence?: 'schema' | 'summary';
 }
 
+export interface DynamicFormGroupedCommandPolicy {
+  orphanFieldExpansion?: 'preserve' | 'medium-and-wide' | 'all';
+  /**
+   * Schema field names whose values are supplied by the surrounding business
+   * context. They remain in the FormGroup and submit payload, but are omitted
+   * from the interactive command layout.
+   */
+  contextFields?: readonly string[];
+}
+
 export interface DynamicFormLayoutPolicy {
   source: DynamicFormLayoutSource;
   preset?: DynamicFormSchemaLayoutPreset;
@@ -126,6 +136,7 @@ export interface DynamicFormLayoutPolicy {
   schemaOperation?: 'detail' | 'create' | 'update' | 'view';
   schemaType?: 'request' | 'response';
   detailSummary?: DynamicFormDetailSummaryPolicy;
+  groupedCommand?: DynamicFormGroupedCommandPolicy;
 }
 ```
 
@@ -215,6 +226,7 @@ Expected behavior:
 - Use full-width rows for long text, descriptions, multiline controls and high-density option controls when needed.
 - Use compact clusters for booleans, short enums and small numeric fields.
 - Expand an otherwise orphan medium/wide field to the full row by default, while preserving compact `xs`/`sm` fields. Use `groupedCommand.orphanFieldExpansion = "preserve"` when the empty space is intentional, or `"all"` when compact orphan fields must also fill the row.
+- Omit fields listed in `groupedCommand.contextFields` from the interactive layout while retaining their schema metadata, runtime control and submit value. Use this only when the surrounding surface already establishes the value, such as a selected employee opening a related-resource command; it is not a substitute for authorization, validation or backend ownership.
 - Keep validation feedback near the field that caused it.
 - Prefer editable controls over presentation roles.
 - Keep command actions visually stable and accessible.