@praxisui/dynamic-form 9.0.61 → 9.0.63

package/README.md

@@ -254,9 +254,15 @@ Recommended defaults:
 - create/edit: `layoutPolicy.source = "schema"`, `intent = "command"`, `preset = "groupedCommand"`, `persistence = "transient"` and a request schema;
 - `groupedCommand` expands a single orphan `md`/`lg` field to the full row by default. Set `layoutPolicy.groupedCommand.orphanFieldExpansion = "preserve"` for intentionally compact rows, or `"all"` to expand orphan `xs`/`sm` fields too;
 - `layoutPolicy.groupedCommand.partialRowStrategy = "fill-compatible"` projects every eligible visual row, including rows created by responsive visibility, CSS `order` and wrapping, to the canonical 12-column grid per container breakpoint, while the default `"preserve"` retains intentional whitespace;
+- generated `groupedCommand` sections are untitled by default, avoiding a generic `Informações` heading beneath an already contextual action title. Explicit semantic group titles published by the schema remain authoritative;
 - dense command drawers: `helpPresentation.display = "auto"` with popover preference for select, checkbox, toggle, date and numeric controls;
 - operational input-heavy forms: `fieldIconPolicy = "presentation-only"` unless the icon is part of the actual affordance.
 
+On narrow viewports, the standard form action footer stacks validation guidance
+above the command CTA and keeps the action full width. This is presentation
+behavior only; submit labels, visibility and confirmation still come from the
+host or discovered action contract.
+
 Schema-driven command forms do not need to declare empty manual sections. Keep host config focused on behavior, messages, actions and field metadata that is genuinely local:
 
 ```ts
@@ -287,7 +293,7 @@ Common inputs:
 
 - `config`, `formId`, `componentInstanceId`
 - `mode`: `create | edit | view`
-- `resourcePath`, `resourceId`, `initialValue`
+- `resourcePath`, `resourceId`, `initialValue`, `emptyState`
 - `schemaUrl`, `readUrl`, `submitUrl`, `submitMethod`, `responseSchemaUrl`
 - `apiEndpointKey`, `apiUrlEntry`
 - `actions`, `layout`, `backConfig`, `hooks`
@@ -297,6 +303,11 @@ Common inputs:
 - `domainRules`
 - `editorialContext`
 
+`actions` is also a registered Dynamic Page input. A host or surface
+materializer may use it for presentation affordances such as a contextual
+submit label and button visibility. It must not use that input to replace the
+schema, method, endpoint or authorization decision discovered from the backend.
+
 In `edit` and `view`, `resourceId` identifies the remote entity to hydrate. In
 `create`, it is contextual only (for example, the employee targeted by an
 item-scoped command) and never starts an entity read; provide command defaults
@@ -304,6 +315,38 @@ through `initialValue`. Component metadata publishes `resourceId` as a public
 input port so top-level and nested `UiCompositionPlan` links are validated by
 the same registry contract used at runtime.
 
+When neither `readUrl` nor `resourcePath` is configured, `initialValue` is the
+authoritative local snapshot: replacing it replaces the whole form value and
+`null` clears stale fields. This is the Dynamic Page composition contract used
+by local master-detail/detail surfaces. With a remote read source, the backend
+entity remains canonical; a later `initialValue` change never resets hydrated
+fields or pending user edits. Change `resourceId` to load another remote entity.
+
+For local master-detail views, `emptyState` is the canonical opt-in placeholder
+while neither `resourceId` nor a non-empty `initialValue` identifies a record.
+The Dynamic Form replaces its field surface with the shared
+`praxis-empty-state-card` only in `mode="view"`; create and edit flows are never
+hidden. The host or `UiCompositionPlan` owns the business-specific copy, while
+the component owns the deterministic transition between "select a record" and
+the presentation-only form. Do not duplicate that state with a consumer-local
+card or keep an empty form visible behind it.
+
+```html
+<praxis-dynamic-form
+  mode="view"
+  [initialValue]="selectedRecord"
+  [emptyState]="{
+    icon: 'touch_app',
+    title: 'Selecione um registro',
+    description: 'Selecione uma linha na tabela para consultar os detalhes.',
+    variant: 'transparent',
+    alignment: 'center',
+    density: 'compact',
+    iconContainer: 'circle'
+  }"
+/>
+```
+
 Common outputs:
 
 - `formSubmit`, `formCancel`, `formReset`