-
-
Notifications
You must be signed in to change notification settings - Fork 245
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
Autosave=true triggering validation immediately #238
Comments
Hello there, thanks for reporting. This may be closely related with #204. Let me investigate this later today, ok? |
Sure thing, no rush - I put a workaround in place which works by not setting autosave until onChange is triggered the first time:
|
@todda00 could you share an example of schema what behaves like this? |
This is the simpler of the 2 I tested it with:
|
Thank you. I'm guessing right now, but it's caused by EDIT 1: It's not. |
I had that thought as well, but I removed the defaultValue from the schema and it still validates immediately. |
Do you know that moment, when you start debugging something and result in rewriting a part of the core functionality? No? We are not similar then. It's fixed now and will be released soon, but it's worth mentioning, that uniforms will be faster now. Like, really faster for bigger forms. All tests are passing, I hope everything works... |
If autosave={true}, the form is validated immediately.
If the autosave is enabled after it is rendered (like the uniforms.tools demo is) then validation does not occur until after the first change, but if its enabled at the time of form render, the validation occurs immediately.
I have tried multiple schemas, and allowed AutoForm to use default field components both with the same results.
Using bootstrap4, Simple Schema 2
The text was updated successfully, but these errors were encountered: