@form-engine-ts/react 2.9.3 → 2.9.5

package/README.md

@@ -75,8 +75,16 @@ set, locale addition becomes a selector containing only unregistered allowed loc
 Visual Builder has two independent design-system extension layers. `components` replaces normalized primitives such as
 `Button`, `TextInput`, `TextArea`, `Select`, `Checkbox`, `Section`, and `Fieldset`. `slots` replaces complete authoring
 surfaces: `toolbar`, `fieldEditor`, `optionEditor`, `pages`, `localization`, or `translationActions`. Slot props expose
-policy-aware `actions`; a custom `translationActions` slot can therefore call an application-specific AI mutation while
-the standard manual localization editors remain unchanged.
+policy-aware `actions` and the builder's resolved `translate(key, params)` function. Feature-aware slots also receive the
+relevant feature state, while localization slots receive policy and translation-adapter availability. A custom
+`translationActions` slot can therefore call an application-specific AI mutation while the standard manual localization
+editors remain unchanged. A slot collection can set `sectionOrder` to arrange `basicSettings`, `completionMessage`,
+`questions`, `addQuestion`, and `localization` as independent authoring sections.
+
+Slot actions include `setManualTranslation(locale, target, property, text)`. It resolves the target's source text and
+existing translation metadata, invokes `createManualTranslationMetadata`, and then stores the translated text and
+generated metadata together. Custom field, page, option, and localization slots should use this action for user-edited
+translations; `setLocaleTranslation` remains available for callers that already provide explicit metadata.
 
 Input primitives receive design-system-friendly `name`, `label`, `required`, `error`, and `helperText` props in addition
 to their normalized string-value callbacks. The `translationActions` slot also receives `translationError`, the latest
@@ -111,8 +119,8 @@ own labels. Builder action icons can be supplied with `renderIcon`, which resolv
     renderHeader: ({ title }) => <MyHeader>{title}</MyHeader>,
     renderPageHeader: ({ page }) => <MyPageHeader page={page} />,
     renderField: (props) => <MyField {...props} />,
-    renderSubmitButton: ({ isSubmitting, onSubmit }) => (
-      <MyButton disabled={isSubmitting} onClick={onSubmit}>Save</MyButton>
+    renderSubmitButton: ({ isSubmitting, disabled, onSubmit }) => (
+      <MyButton loading={isSubmitting} disabled={disabled} onClick={onSubmit}>Save</MyButton>
     ),
     renderSubmitError: ({ error, onRetry }) => <MyError error={error} onRetry={onRetry} />
   }}
@@ -121,7 +129,11 @@ own labels. Builder action icons can be supplied with `renderIcon`, which resolv
 
 Validation runs before `beforeSubmit`. A `"cancel"` result does not call `onSubmit` and preserves values and drafts.
 Header, page-header, field, navigation, submit, validation-summary, completion, and submit-error slots can replace the
-default UI. The localized `completionMessage` is displayed after a successful submission.
+default UI. The localized `completionMessage` is displayed after a successful submission. Set
+`successRenderMode="replace"` to remove the questions, navigation, and submit button after success and focus the
+completion status region; the default `"append"` mode preserves the existing form UI. `hideFormOnSuccess` is retained
+as a deprecated alias for `successRenderMode="replace"`. The submit-button slot receives `submitStatus` and `disabled`
+in addition to `isSubmitting` and `onSubmit`.
 
 Pass ordered `submissionGuards` to allow, block, or require confirmation before `onSubmit`. Confirmation receives all
 guard findings through `renderSubmissionConfirmation`. A `receiptStore` prevents accidental repeat submissions and can