FormForgeBuilder

FormForgeBuilder provides a form-definition editing UI.

<FormForgeBuilder
  v-model="model"
  :autosave="true"
  :autosave-delay="5000"
/>

Builder model shape

{
  uuid: string | null,
  key: string | null,
  title: string,
  category: string | null,
  pages: FormForgePageSchema[],
  conditions: FormForgeCondition[],
  drafts: { enabled: boolean }
}

Typical usage

• create a new form definition
• patch an existing form definition
• publish and unpublish revisions

UI control props

Use disable-style props to remove specific controls when embedding builder in constrained admin UIs.

• disableTitleInput (false)
• disableCategoryControl (false)
• disablePublishAction (false)
• formRouteKey (undefined) load first form from a configured form-routes/{key} endpoint when loadFormKey is not provided
• categoryRouteKey (undefined) load categories from category-routes/{key}

Publication default:

• defaultPublished (false)

<FormForgeBuilder
  v-model="model"
  :disable-title-input="true"
  :disable-category-control="true"
  :disable-publish-action="false"
  :default-published="true"
/>

Publish behavior

• defaultPublished no longer triggers a separate /publish request after save
• builder save now supports autoPublish and sends auto_publish in create/patch payloads
• when defaultPublished is true, publish intent is handled directly in save payload flow

Migration note

If your integration relied on a second publish network call after save, update expectations:

• create/patch can directly return a published revision through auto_publish
• do not rely on a separate publish request for post-save side effects