You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently using the @quillforms/renderer-core library for a project and I have encountered an issue regarding the implementation of jump logics. Below is the code snippet I'm working with:
"@quillforms/react-renderer-utils": "^5.9.1" and React 18.2.0
Despite following the documentation, the jump logics in my form do not seem to be functioning as expected. I have set up the form logic and blocks according to the library's guidelines, but the form isn't responding to the specified conditions, it gets stucked in the first screen, Ok button is not taking me to the next page.
Is there a specific aspect of the jump logic implementation that I might be missing, or is this feature fully supported in the current version of the library? Any guidance or insights you can provide would be greatly appreciated.
Thank you for your time and assistance.
The text was updated successfully, but these errors were encountered:
This feature was supported in a private library.
I don't know how you have had set up the logic parameter in the formObj.
But, I do think to support the jump logic and calculator in the open source version.
Hello,
I am currently using the @quillforms/renderer-core library for a project and I have encountered an issue regarding the implementation of jump logics. Below is the code snippet I'm working with:
"@quillforms/react-renderer-utils": "^5.9.1" and React 18.2.0
Despite following the documentation, the jump logics in my form do not seem to be functioning as expected. I have set up the form logic and blocks according to the library's guidelines, but the form isn't responding to the specified conditions, it gets stucked in the first screen, Ok button is not taking me to the next page.
Is there a specific aspect of the jump logic implementation that I might be missing, or is this feature fully supported in the current version of the library? Any guidance or insights you can provide would be greatly appreciated.
Thank you for your time and assistance.
The text was updated successfully, but these errors were encountered: