@form-engine-ts/core 4.4.0 → 4.6.0

package/README.md

@@ -53,6 +53,22 @@ safe maximum-length corrections while purging unregistered locale content. Pass
 `{ policy: { allowedLocales, maxLocales } }` to `populateSchemaTranslations` to reject inadmissible targets before the
 translation adapter runs.
 
+Fields can use a `displayRule` with nested `all`/`any` condition groups and `show` or `hide` actions. Supported
+operators include equality, containment, emptiness, and numeric comparisons; the legacy `displayCondition` and
+`not_empty` forms remain supported. `submissionSettings` can enable pre-submit confirmation and select its
+`dialog`, `inline`, or `replace` presentation.
+
+`collectTranslationSlots`, `computeSourceTextHash`, and `getTranslationStatus` expose canonical translation targets
+and missing, translated, stale, or manual states for authoring tools. `populateSchemaTranslations` can populate stale
+and missing entries while preserving manual translations and reports skipped reasons.
+
+Legacy translation metadata can be recognized with `isManualTranslationMetadata` and migrated with
+`migrateSchemaTranslationMetadata`; pass a custom migrator when legacy fields need application-specific conversion.
+`PopulateTranslationsOptions` is a compatibility alias for `PopulateTranslationOptions`, which also accepts custom
+manual-translation detection and metadata normalization callbacks. `removeLocaleFromSchema(schema, locale)` removes
+the locale from registrations and all form, page, field, option translation values and metadata; the default locale
+cannot be removed.
+
 The React builder uses canonical keys with legacy aliases when resolving UI translations:
 
 | Canonical key | Legacy alias |