@praxisui/dynamic-form 3.0.0-beta.8 → 4.0.0-beta.0
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 +5 -0
- package/fesm2022/praxisui-dynamic-form.mjs +564 -191
- package/index.d.ts +56 -6
- package/package.json +7 -7
- package/fesm2022/praxisui-dynamic-form.mjs.map +0 -1
package/README.md
CHANGED
|
@@ -56,6 +56,10 @@ last_updated: "2026-03-22"
|
|
|
56
56
|
- Keep runtime customization and layout governance inside the host application
|
|
57
57
|
- Integrate with other `@praxisui/*` packages through shared contracts and settings flows
|
|
58
58
|
|
|
59
|
+
## Canonical submit contract
|
|
60
|
+
|
|
61
|
+
When the host opens the form from backend `surfaces` or `actions`, the canonical runtime path is `schemaUrl + submitUrl + submitMethod`, and detached hosts may also pass `apiUrlEntry` when the current overlay does not inherit the route-scoped `API_URL`. The legacy `crud.create/update` fallback still exists only as transitional behavior for hosts that have not fully migrated to discovery-driven submit execution.
|
|
62
|
+
|
|
59
63
|
## Install
|
|
60
64
|
|
|
61
65
|
```bash
|
|
@@ -131,6 +135,7 @@ export class FormDemoComponent {
|
|
|
131
135
|
```
|
|
132
136
|
|
|
133
137
|
Tip: connect to a backend resource by setting `resourcePath`/`resourceId`. The component can fetch schemas and reconcile local layout with server metadata when `enableCustomization` is true.
|
|
138
|
+
For metadata-driven surfaces published by the backend, prefer passing `schemaUrl`, `submitUrl` and `submitMethod` explicitly. In dialog/drawer hosts detached from the route injector, pass `apiUrlEntry` in addition to `apiEndpointKey` so relative runtime URLs still resolve against the remote backend instead of the local shell origin.
|
|
134
139
|
When a late `config` hydration rebuilds the surface, the runtime preserves the current form values already mounted in memory only when the logical context remains the same (`resourcePath`, `resourceId`, and mode). If the form was preloaded from `resourceId`, that entity hydration remains visible after the rebuild only for the same entity context; entity switches and create-mode transitions do not restore the previous record snapshot.
|
|
135
140
|
|
|
136
141
|
Presentation/read-only note:
|