@praxisui/dynamic-form 9.0.0-beta.41 → 9.0.0-beta.43
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 +13 -0
- package/ai/component-registry.json +31 -9
- package/docs/schema-driven-layout-materialization-rfc.md +7 -1
- package/fesm2022/praxisui-dynamic-form.mjs +59 -7
- package/package.json +8 -8
- package/src/lib/praxis-dynamic-form.json-api.md +7 -1
- package/types/praxisui-dynamic-form.d.ts +2 -0
package/README.md
CHANGED
|
@@ -140,6 +140,19 @@ 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
|
+
In runtime rendering, compact detail containers are kept visible only when at least one referenced
|
|
144
|
+
field can actually be materialized after metadata visibility, `visible=false`, `hidden=true` and
|
|
145
|
+
field-rule overrides are applied. Boolean detail fields are valid presentation content, including
|
|
146
|
+
`false` values; marker/flag groups should render their boolean values, not collapse them as empty
|
|
147
|
+
strings. If a section has no materialized fields, the runtime hides the section instead of leaving
|
|
148
|
+
an orphan title.
|
|
149
|
+
When a migrated detail surface needs the summary density to win over generic schema widths, set
|
|
150
|
+
`detailSummary.widthPrecedence: "summary"` together with `columns` or `responsiveColumns`. The
|
|
151
|
+
default is `"schema"`, so existing forms keep honoring `x-ui.width` unless the summary policy
|
|
152
|
+
explicitly opts into overriding it for the compact read-only surface.
|
|
153
|
+
Use `"summary"` for curated operational summaries. If a field contains long narrative text,
|
|
154
|
+
legal content, observations, or values that require scan width, keep schema precedence for that
|
|
155
|
+
surface or exclude the field from the compact summary and expose it in a secondary detail group.
|
|
143
156
|
|
|
144
157
|
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
158
|
|