-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot edit the existing components #136
Comments
@kyuukyuusheinmoe can you create a short reproducible repo example please. Your example doesn’t give me enough to start an investigation. see you |
@Romakita formio.compo.edit.error.mov |
@Romakita , I found out the bug that it is because I used form builder as the component of React Hook Form. That's really insane to use form builder component under another form in order to get changed component values. It's my bad. Whenever saving component event it used the parent's container and components in order to check if the new or edited component existed in parent's component list. First creating the component by dragging is ok and that component is in parent's component list. But editing the dragged component cannot be found in parent's component list that's why getting null. Maybe because of conflicting in finding its parent because we already have two one is from React Hook Form and another is from Formio.According my assumption, I took the builder out from RHF form component, it solved me the issue. Let me close the issue then. |
It was just the bad usage of form Builder component under as the children of React Hook Form Component to maintain the form values without considering Form Builder is also a form and just thought it's just the react component. |
Information
I have created a few components in form builder. After that, I need some modifications on the components that just have been created and I do some updates. Then I tried to save and the component editor form seem cracked. In the error console, it's showing the message
Example
Acceptance criteria
The text was updated successfully, but these errors were encountered: