-
Notifications
You must be signed in to change notification settings - Fork 42
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 conditions still triggering a server side error #183
Comments
Hey @MattDion, I'm able to reproduce your issue. Looks like it happens with conditions by configurations only, and only when the conditions are all by configurations for a given field. I'll have a look at a fix as soon as I can :) Thanks for reporting! 👍 |
@MattDion the new release (1.3.2.1) fixes this issue. Thanks again :) |
Thank you for the new release!!! It works perfect!! We might have add a very nice feature. and will fork soon ;) |
@MattDion cool :) what is this feature? Something that might be applicable for the core? |
Followed the documentation:
https://github.com/kjac/FormEditor/blob/master/Docs/extend_condition.md
https://github.com/kjac/FormEditor/blob/master/Docs/extend_condition_advanced.md
https://github.com/kjac/FormEditor/blob/master/Docs/extend_condition_simple.md
But I can’t figure out how to not trigger some sort of server side validation
The client side validation is working as expected, however server side validation still gets triggered. Example of the results being returned:
{"invalidFields":[],"failedValidations":[{"rules":[{"field":{"name":"Text box","formSafeName":"_Text_box","submittedValue":"qweqweqweqwe","invalid":false},"condition":{"type":"my.length"}}],"errorMessage":"length!!!","invalid":true}]}
The text was updated successfully, but these errors were encountered: