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
Before, the code in the then promise would never be executed if the form had errors. However, I can see that after the update, the catch is never triggered, and the logic always continued in then. As a temporary fix, I reverted to evaluating the result, as suggested in #179, but I hope this will be fixed eventually.
Steps To Reproduce:
You can visit the website of the package and try out the example titled as "Validate Form Before Submit", you will see that it always returns "Form Submitted!" even though the form contains plenty of errors.
The text was updated successfully, but these errors were encountered:
The behavior was changed, to resolve to boolean instead, since rejections could mask other underlying errors. also with the upcoming async/await feature it is more friendly than having to catch the errors.
Versions:
Description:
After updating from
2.0.0-rc.5
to2.0.0-rc.6
I noticed strange behavior with my form. When submitted, it is being validated as follows:Before, the code in the
then
promise would never be executed if the form had errors. However, I can see that after the update, thecatch
is never triggered, and the logic always continued inthen
. As a temporary fix, I reverted to evaluating the result, as suggested in #179, but I hope this will be fixed eventually.Steps To Reproduce:
You can visit the website of the package and try out the example titled as "Validate Form Before Submit", you will see that it always returns "Form Submitted!" even though the form contains plenty of errors.
The text was updated successfully, but these errors were encountered: