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
first of all thanks for your effort on this library, I think it can save lots of time, also for quite complicated forms.
When implementing it in our multi-step, nested form I encountered a few situations where I'd personally like to see the API extended or bugs fixed. So I'll open some issues regarding feature proposals and bug reports, let me know if I can help out with fixing those.
So first of all, I'd find it really cool if error messages would bubble up. Consider a wizard-like form, let's say for placing an order for the first time. You'll have to enter payment details, shipping address, possibly billing address, some signup data etc. I can make a nested form like this (form field definitions not included because they are quite verbose):
Now, if I don't want to force my users to complete one step after another (because they are independent), I'd like to show the invalid parts of the order form along with actual error messages in the confirm step. Currently I can't do that. I can iterate through the fields and check field.isValid and then print a generic message. But what would be nicer in my opinion is if the error field would be an array, and nested errors bubble up, similar to the isValid flag.
I hope that makes sense, let me know what you think.
The text was updated successfully, but these errors were encountered:
Hi,
first of all thanks for your effort on this library, I think it can save lots of time, also for quite complicated forms.
When implementing it in our multi-step, nested form I encountered a few situations where I'd personally like to see the API extended or bugs fixed. So I'll open some issues regarding feature proposals and bug reports, let me know if I can help out with fixing those.
So first of all, I'd find it really cool if error messages would bubble up. Consider a wizard-like form, let's say for placing an order for the first time. You'll have to enter payment details, shipping address, possibly billing address, some signup data etc. I can make a nested form like this (form field definitions not included because they are quite verbose):
(I hope you get the idea.)
Now, if I don't want to force my users to complete one step after another (because they are independent), I'd like to show the invalid parts of the order form along with actual error messages in the confirm step. Currently I can't do that. I can iterate through the fields and check
field.isValid
and then print a generic message. But what would be nicer in my opinion is if theerror
field would be an array, and nested errors bubble up, similar to theisValid
flag.I hope that makes sense, let me know what you think.
The text was updated successfully, but these errors were encountered: