/**
     * Arbitrary context passed to the onSuccess callback.
     */ /**
     * The form state that was sent with the request when retrieving the `json` arg.
     */ /**
   * If you would like to solely leverage server-side validation on submit,
   * you can disable checks that the form makes before it submits
   */ /**
   * If you don't want the form to be a <form> element, you can pass a string here to use as the wrapper element.
   */ /**
   * By default, the form will get the field schema (not data) from the current document. If you pass this in, you can override that behavior.
   * This is very useful for sub-forms, where the form's field schema is not necessarily the field schema of the current document (e.g. for the Blocks
   * feature of the Lexical Rich Text field)
   */ /**
   * Determines if this Form is the main, top-level Form of a document. If set to true, the
   * Form's children will be wrapped in a DocumentFormContext, which lets you access this document
   * Form's data and fields from any child component - even if that child component is wrapped in a child
   * Form (e.g. a lexical block).
   */ /**
   * If you want to pass additional data to the onSuccess callback, you can use this context object.
   *
   * @experimental This property is experimental and may change in the future.
   */ /**
   * When true, will disable the form while it is processing.
   * @default true
   */ /**
   * When true, will disable the success toast after form submission.
   * @default false
   */ /**
   * When true, will skip validation before submitting the form.
   * @default false
   */ /**
 * Returns the form state and the response from the server.
 *
 * @experimental - Note: the `{ res: ... }` return type is experimental and may change in the future. Use at your own risk.
 */ /**
   * If mergeOverrideData true, the data will be merged with the existing data in the form state.
   * @default true
   */ /**
     * If provided, will use this instead of of derived data from the current form state.
     */ /**
   * If `sanitize` is true, default values will be set for form field properties that are not present in the incoming state.
   * For example, `valid` will be set to true if it is not present in the incoming state.
   */ export { }; /**
   * Form context fields may be outdated and should not be relied on. Instead, prefer `useFormFields`.
   */  /**
   * Tracks wether the form state passes validation.
   * For example the state could be submitted but invalid as field errors have been returned.
   */  /**
   * If the form has started processing in the background (e.g.
   * if autosave is running), this will be true.
   */ 

//# sourceMappingURL=types.js.map