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
{{ message }}
This repository has been archived by the owner on Jan 1, 2020. It is now read-only.
Thank you for this awesome package! I'm using this in my project powering 4 forms of different sizes and I'm really happy how easily configurable and re-usable it is.
There's a wonderful option of reading globalErrors after form submission fails due to a backend error. It would be even better if this error could automatically reset if any of the internal field values changed.
Use case:
In a simple login form, I can read the globalErrors prop to check & handle the most common post-submit error: invalid credentials. This error, once shown, stays shown until the next time form submit succeeds, or results in a different error. Until then, the error message stays put. I believe it could be better UX if the error disappears (reset internally) as the user interacts with the form fields to change/correct their login credentials.
The text was updated successfully, but these errors were encountered:
This would allow to customise the behaviour according to your needs which feels more in line with react-reform's philosophy of not being too opinionated.
Thank you for this awesome package! I'm using this in my project powering 4 forms of different sizes and I'm really happy how easily configurable and re-usable it is.
There's a wonderful option of reading
globalErrors
after form submission fails due to a backend error. It would be even better if this error could automatically reset if any of the internal field values changed.Use case:
In a simple login form, I can read the
globalErrors
prop to check & handle the most common post-submit error: invalid credentials. This error, once shown, stays shown until the next time form submit succeeds, or results in a different error. Until then, the error message stays put. I believe it could be better UX if the error disappears (reset internally) as the user interacts with the form fields to change/correct their login credentials.The text was updated successfully, but these errors were encountered: