@praxisui/dynamic-form 9.0.0-beta.11 → 9.0.0-beta.14
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 +33 -1
- package/ai/component-registry.json +13311 -0
- package/fesm2022/praxisui-dynamic-form.mjs +24 -12
- package/package.json +12 -9
package/README.md
CHANGED
|
@@ -26,7 +26,7 @@ npm i @praxisui/dynamic-form@latest
|
|
|
26
26
|
Peer dependencies:
|
|
27
27
|
|
|
28
28
|
- `@angular/common`, `@angular/core`, `@angular/forms`, `@angular/cdk`, `@angular/material`, `@angular/router` `^21.0.0`
|
|
29
|
-
- `@praxisui/ai`, `@praxisui/core`, `@praxisui/dynamic-fields`, `@praxisui/metadata-editor`, `@praxisui/rich-content`, `@praxisui/settings-panel`, `@praxisui/visual-builder` `^9.0.0-beta.
|
|
29
|
+
- `@praxisui/ai`, `@praxisui/core`, `@praxisui/dynamic-fields`, `@praxisui/metadata-editor`, `@praxisui/rich-content`, `@praxisui/settings-panel`, `@praxisui/visual-builder` `^9.0.0-beta.12`
|
|
30
30
|
- `rxjs` `^7.8.0`
|
|
31
31
|
|
|
32
32
|
## Minimum Local Runtime
|
|
@@ -101,6 +101,38 @@ For schema-driven backend surfaces, prefer explicit `schemaUrl`, `submitUrl`, an
|
|
|
101
101
|
|
|
102
102
|
When using resource, schema, read, or submit flows, the host must provide the effective API/CRUD service wiring for that scope.
|
|
103
103
|
|
|
104
|
+
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.
|
|
105
|
+
|
|
106
|
+
Example backend-owned `x-ui` metadata:
|
|
107
|
+
|
|
108
|
+
```json
|
|
109
|
+
{
|
|
110
|
+
"type": "object",
|
|
111
|
+
"properties": {
|
|
112
|
+
"frequencyType": {
|
|
113
|
+
"type": "string",
|
|
114
|
+
"x-ui": {
|
|
115
|
+
"label": "Frequency type",
|
|
116
|
+
"controlType": "async-select",
|
|
117
|
+
"helpText": "Select the operational class used by payroll and timekeeping rules.",
|
|
118
|
+
"tooltip": "Backend-owned DTO semantics; local FormConfig cannot override it.",
|
|
119
|
+
"tooltipOnHover": true,
|
|
120
|
+
"icon": "calendar_month",
|
|
121
|
+
"iconPosition": "start",
|
|
122
|
+
"iconColor": "primary",
|
|
123
|
+
"endpoint": "/api/frequency-types/options/filter",
|
|
124
|
+
"filterField": "name",
|
|
125
|
+
"sortField": "name",
|
|
126
|
+
"sortOrder": "asc",
|
|
127
|
+
"optionsPageSize": 20
|
|
128
|
+
}
|
|
129
|
+
}
|
|
130
|
+
}
|
|
131
|
+
}
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
In that flow, local `FormConfig` may place `frequencyType` in sections, rows, tabs, custom actions, or corporate-only local fields. It should not persist competing `label`, `helpText`, `tooltip`, or icon metadata for `frequencyType`, because the next schema reconciliation will restore the backend DTO semantics.
|
|
135
|
+
|
|
104
136
|
## Runtime Inputs And Outputs
|
|
105
137
|
|
|
106
138
|
Common inputs:
|