@praxisui/dynamic-form 9.0.0-beta.30 → 9.0.0-beta.31

package/README.md

@@ -188,6 +188,28 @@ Recommended defaults:
 - 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.
 
+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
+const commandConfig: FormConfig = {
+  metadata: { source: 'schema' },
+  behavior: {
+    disableMountAnimation: true,
+    focusFirstError: true,
+    scrollToErrors: true,
+  },
+  messages: {
+    submitSuccess: 'Registro salvo.',
+    submitError: 'Não foi possível salvar o registro.',
+  },
+};
+```
+
+Pair this config with an explicit schema source, such as `[schemaUrl]`,
+`[submitUrl]`, `[submitMethod]` and, in detached hosts, `[apiEndpointKey]` or
+`[apiUrlEntry]`. A sectionless config is valid only when the schema/runtime
+source is the canonical owner of field grouping and controls.
+
 Do not use Angular config to fix weak DTO semantics. Missing grouping, vague `helpText`, generic labels, raw coded values, wrong control types or absent option metadata should return to backend DTO/schema hardening. The detailed migration checklist lives in `docs/schema-driven-layout-materialization-rfc.md`.
 
 ## Runtime Inputs And Outputs