@praxisui/dynamic-form 9.0.4-rc.46 → 9.0.4-rc.47

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -226,6 +226,7 @@ Expected behavior:
226
226
  - Use full-width rows for long text, descriptions, multiline controls and high-density option controls when needed.
227
227
  - Use compact clusters for booleans, short enums and small numeric fields.
228
228
  - 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.
229
+ - Preserve multi-field partial rows by default. `groupedCommand.partialRowStrategy = "fill-compatible"` distributes the remainder deterministically through canonical spans (`3`, `4`, `6`, `8`, `12`) at each container breakpoint. It does not mutate schema widths or authoring documents; compact boolean/action controls, uploads and unknown control types are ineligible.
229
230
  - 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.
230
231
  - Keep validation feedback near the field that caused it.
231
232
  - Prefer editable controls over presentation roles.
@@ -234,6 +235,11 @@ Expected behavior:
234
235
 
235
236
  This preset is the platform replacement for local create/edit `FormConfig.sections` when the backend command DTO already publishes sufficient `@UISchema` metadata.
236
237
 
238
+ The runtime recomputes the projection from currently visible columns. Thus a rule-hidden field may
239
+ cause two remaining compatible fields to become `6 + 6`, while restoring the field restores the
240
+ original row projection. Responsive hiding is evaluated against the form-row container rather than
241
+ the browser viewport.
242
+
237
243
  ### `default`
238
244
 
239
245
  Preserve current generated behavior for consumers that only need a basic generated layout.