-
Notifications
You must be signed in to change notification settings - Fork 474
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
[Custom Components] Problem with advanced logic #1045
Comments
Hi... @adhonay, I hope you are doing well. |
Now that I saw your question, were you able to resolve it? I received the notification when they marked the @lane-formio and @Sidiro23 no error. And I still don't know if it was resolved, I had to stop the project precisely because there was a conflict in the custom components and additional logic native to Formio. |
Would it be possible to provide a code sandbox to help triage this? |
Hi @adhonay, The other thing is, because we need to override the edit form to add out own fields to it, the advance logic stops working. There are some other issues as well. I believe you have mentioned that advance logic has problems. I was just wanted to double-check if you were able to figure it out or if there is a hack for that. |
abrir chamado com bug da logica adicional
Environment
Please provide as many details as you can:
formiojs": "4.18.0
formio/angular":" 6.0.0
Node: 18.18.0
Npm 10.1.0
I created several customized components, as done in the documentation, but I have a serious problem.
If I add any type of advanced logic, the custom component starts to disregard all the logic I implemented in the editform.
For example:
Does anyone know how I can configure my logic implemented via code in editform along with formio's advanced logic?
Configuring my customcomponent.formio.ts
To simulate the error, simply create a customized component, add any logic to that component's editform file, and later create advanced logic through the configuration modal. The logic created in the editform file will not work, nor will it even execute.
The text was updated successfully, but these errors were encountered: