FormBuilder onChange callback not triggered when options prop is provided

未关闭
#631 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@Victoriya25 已经在做这个了。

开始于 2025年12月17日。

评估

这个 Issue 还没有评估数据。

描述

Describe the bug
The onChange callback of FormBuilder from @formio/react is not triggered when the options prop is provided. This happens even if options is an empty object (options={{}}). As soon as options is set, form changes made in the builder UI no longer invoke the onChange handler.

Version/Branch
@formio/react: "6.1.1"
Framework: Next.js (App/Pages Router)
Rendering: client-side only (ssr: false via dynamic import)

To Reproduce
Steps to reproduce the behavior:

  1. Create a Next.js project and dynamically import FormBuilder:
   const FormBuilder = dynamic(
     () => import('@formio/react').then((module) => module.FormBuilder),
     { ssr: false }
   )
  1. Define a simple onChange callback:
const handleFormChange = (schema: FormType) => {
  console.log('i handled the change')
}
  1. Render FormBuilder with initialForm, onChange, and any options prop (even an empty object):
<FormBuilder
  initialForm={initialForm}
  onChange={handleFormChange}
  options={{}}
/>

(The same issue occurs with a fully customized options.builder configuration.)

  1. Interact with the FormBuilder UI (add/remove/update components).
  2. Observe that handleFormChange is never called.

Expected behavior
The onChange callback should be triggered whenever the form schema changes in the FormBuilder, regardless of whether the options prop is provided (including options={{}}).

主要语言
TypeScript
星标
371
派生
309
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

formio/react 的其他 Issue

查看 formio/react 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。