-
Notifications
You must be signed in to change notification settings - Fork 123
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
Empty errors with two level nested form using version 4.5.0 #173
Comments
+1 on facing the same issue in this upgrade |
Can you please try main and let me know? If it works I will ship a new release asap. :) |
I can verify that the commit solved the problem for us :) |
Also confirmed that this commit solved the problem. |
Works for me as well. Thanks Jose! ❤️ |
4.5.1 is out, enjoy! ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was using version 4.4.3 version and everything was working fine. After I migrated to version 4.5.0 the errors in the deepest nested form weren't shown.
Example:
After checking the latest changes I found this:
a9e1a3d#diff-097986c2a86bfdab8c54b295763f1a6d47b1e86bf91bb9618715fc82b5661269R65
If I am not missing something, this only works with just one level nested form because the parent form action is present. Two-level nested form will not shown the errors because the parent form is the one-level nested form which has action nil.
Any thoughts on this? Should this be setting the action in child nested forms to avoid this?
Please let me know if I am missing something.
The text was updated successfully, but these errors were encountered: