@praxisui/dynamic-fields 9.0.0-beta.8 → 9.0.0-beta.80

package/README.md

@@ -26,7 +26,7 @@ npm i @praxisui/dynamic-fields@latest
 Peer dependencies:
 
 - `@angular/common`, `@angular/core`, `@angular/forms`, `@angular/material`, `@angular/cdk`, `@angular/platform-browser`, `@angular/router` `^21.0.0`
-- `@praxisui/core`, `@praxisui/cron-builder` `^9.0.0-beta.4`
+- `@praxisui/core`, `@praxisui/cron-builder` `^9.0.0-beta.12`
 - `rxjs` `^7.8.0`
 
 ## Provide Defaults
@@ -162,6 +162,14 @@ Read-only and display states prefer the canonical `field.valuePresentation` cont
 
 Use `valuePresentation` for scalar display values such as currency, number, date, datetime, time, percentage, and boolean. Keep legacy hints such as `format`, `numericFormat`, `currency`, `numberFormat`, and `locale` only as compatibility inputs when needed.
 
+Presentation formatting resolves locale in this order: `field.localization.locale`, `field.locale`, the canonical `PraxisI18nService` locale, Angular `LOCALE_ID`, then `en-US`. Host applications should configure the Praxis i18n service or field metadata instead of patching display labels locally.
+
+Presentation mode can also consume `field.presentation` and `field.presentationRules` for semantic readonly display states such as status, chip, badge, icon+value, tone, icon, label, badge, tooltip, and appearance. `presentationRules` use canonical Json Logic and must only produce semantic display patches; they do not mutate the `FormControl`, submit payload, or execute arbitrary actions.
+
+For compact enterprise indicators, `field.presentation.presenter = 'microVisualization'` renders the canonical `presentation.visualization` contract in pure presentation mode. The dynamic-fields runtime owns this compact HTML renderer so forms, lists, and tables can share the same metadata without depending on chart components for virtualized or readonly cells. Use it for small comparison, stacked bar, bullet, and delta indicators; use `@praxisui/charts` when the host needs a richer chart widget outside the field presentation pipeline.
+
+Runtime support for these metadata paths is canonical. Visual editor coverage is a separate layer and should be verified before claiming authoring parity.
+
 ## Inline Filters
 
 The package also exports inline field components for compact filter and toolbar experiences, including inline text, select, async select, entity lookup, numeric, currency, date, date range, time, rating, and specialized business filters.
@@ -203,5 +211,5 @@ Main exports:
 
 - Keep host custom fields explicit: runtime registration and editorial metadata are both required for a complete experience.
 - Do not patch package-owned controls only in a consuming host; fix the canonical registry/editorial chain.
-- Use Material Design 3 tokens from the host theme for surfaces, text, outline, semantic colors, and overlay contrast.
+- Use the semantic `--praxis-theme-*` roles from the host theme for surfaces, text, outline, focus, elevation, and overlay contrast. Dynamic Fields keeps Material Design 3 tokens only as fallbacks, so hosts do not need to target package internals to support light and dark themes.
 - Use the official documentation for field catalogs, selection guidance, inline filter contracts, and custom-field troubleshooting.