@praxisui/dynamic-form 9.0.0-beta.77 → 9.0.0-beta.78
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
|
@@ -160,6 +160,15 @@ Field-level access metadata follows the same authority boundary. When the backen
|
|
|
160
160
|
|
|
161
161
|
Dense operational forms should keep DTO `hint`/`helpText` intact and use `FormConfig.helpPresentation` to choose the visual policy. For drawers or command forms, prefer `display: "auto"` with `preferPopoverForControls` for controls such as `toggle`, `checkbox`, and `select`; validation errors remain inline regardless of this policy. Field-level `helpDisplay` is still authoritative when present, including `helpDisplay: "auto"` for DTOs that need a local threshold.
|
|
162
162
|
|
|
163
|
+
Submit failures published in the Praxis `RestApiResponse.errors` envelope are materialized by the
|
|
164
|
+
runtime. A safe public `message` is shown to the user, while an error with a `target` matching a
|
|
165
|
+
form control is also attached to that control and marked as touched. Existing client validators
|
|
166
|
+
are preserved, and only the previous server error is cleared before a new submit attempt. Targets
|
|
167
|
+
may use Angular dotted paths or JSON Pointer syntax. Unknown targets remain form-level feedback;
|
|
168
|
+
the client does not guess a field from error text, codes, keywords, or private database details.
|
|
169
|
+
Generic network, validation, server, and save fallbacks use the platform i18n keys under
|
|
170
|
+
`global.submitError.*`; backend-owned business messages remain authoritative.
|
|
171
|
+
|
|
163
172
|
Example backend-owned `x-ui` metadata:
|
|
164
173
|
|
|
165
174
|
```json
|