@praxisui/dynamic-form 9.0.0-beta.41 → 9.0.0-beta.42

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.
package/README.md CHANGED
@@ -140,6 +140,13 @@ fieldsets can render multiple read-only fields per row. Fields without an explic
140
140
  full-width to preserve existing layouts. Generated compact sections also receive semantic header
141
141
  icons derived from their group role, while field icons continue to come from existing schema
142
142
  metadata.
143
+ When a migrated detail surface needs the summary density to win over generic schema widths, set
144
+ `detailSummary.widthPrecedence: "summary"` together with `columns` or `responsiveColumns`. The
145
+ default is `"schema"`, so existing forms keep honoring `x-ui.width` unless the summary policy
146
+ explicitly opts into overriding it for the compact read-only surface.
147
+ Use `"summary"` for curated operational summaries. If a field contains long narrative text,
148
+ legal content, observations, or values that require scan width, keep schema precedence for that
149
+ surface or exclude the field from the compact summary and expose it in a secondary detail group.
143
150
 
144
151
  For fields published by the backend schema, server DTO metadata remains authoritative for semantic presentation data such as `label`, `hint`, `helpText`, `tooltip`, `tooltipOnHover`, and icon metadata. Local `FormConfig` should customize layout, grouping, transient fields, actions, and host-specific behavior, but it should not redefine DTO-owned field semantics.
145
152