@praxisui/dynamic-form 3.0.0-beta.9 → 5.0.0-beta.0

package/README.md

@@ -56,6 +56,10 @@ last_updated: "2026-03-22"
 - Keep runtime customization and layout governance inside the host application
 - Integrate with other `@praxisui/*` packages through shared contracts and settings flows
 
+## Canonical submit contract
+
+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.
+
 ## Install
 
 ```bash
@@ -67,8 +71,6 @@ Peer dependencies (Angular v20):
 - `@angular/common` `^20.0.0`
 - `@angular/cdk` `^20.0.0`
 - `@praxisui/core` `^0.0.1`
-- `@praxisui/specification-core` `^0.0.1`
-- `@praxisui/specification` `^0.0.1`
 - `@praxisui/visual-builder` `^0.0.1`
 - `@praxisui/settings-panel` `^0.0.1`
 - `@praxisui/cron-builder` `^0.0.1`
@@ -131,6 +133,7 @@ export class FormDemoComponent {
 ```
 
 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.
+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.
 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.
 
 Presentation/read-only note:
@@ -446,7 +449,7 @@ Os paths micro são normalizados para `fieldMetadata[].<prop>` para garantir que
 
 ## Regras de formulário (novo contrato)
 
-- Formato: cada regra tem `targetType` (`field | section | action | row | column`), `targets: string[]` (IDs canônicos do alvo), e `effect` com `condition` (DSL ou Specification), `properties` e `propertiesWhenFalse`.
+- Formato: cada regra tem `targetType` (`field | section | action | row | column`), `targets: string[]` (IDs canônicos do alvo), e `effect` com `condition` (`JsonLogicExpression | null`), `properties` e `propertiesWhenFalse`.
 - Compatibilidade: regras antigas (`context/targetField`) são migradas para `properties/targets` automaticamente; prefixes legados `section:/action:/row:/column:` continuam sendo normalizados quando representarem alvos tradicionais. Para header actions de seção, o ID canônico é preservado como `section:<sectionId>:header-action:<actionLogicalId>`.
 - Semântica de limpeza: valores `null` em `properties/propertiesWhenFalse` removem o override e retornam ao valor base do layout; ausência mantém o valor base.
 - Whitelist por tipo (somente propriedades a seguir são aplicadas; demais são descartadas e logadas em dev):