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
I'm having a field day with this library, it's without a doubt the best form library I've ever seen.
I'm particularly fond of the async validation functions that are available in the fields, with built-in debouncing. One problem that I noticed in a specific use-case which I believe should happen to other users is the following:
I have a validation to be performed to check if a field is a duplicate in the API. So to save resources, I only call the API when the field is valid, and apply debounce, displaying a loading state when isValidating is true. The thing is - the loader is displayed even when I don't have to call the API (field is not valid yet). Is there anything I can do now to prevent that behavior? setting onChange validator doesn't help because I don't want to display the error until the field is valid or the user submitted.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm having a field day with this library, it's without a doubt the best form library I've ever seen.
I'm particularly fond of the async validation functions that are available in the fields, with built-in debouncing. One problem that I noticed in a specific use-case which I believe should happen to other users is the following:
I have a validation to be performed to check if a field is a duplicate in the API. So to save resources, I only call the API when the field is valid, and apply debounce, displaying a loading state when isValidating is true. The thing is - the loader is displayed even when I don't have to call the API (field is not valid yet). Is there anything I can do now to prevent that behavior? setting onChange validator doesn't help because I don't want to display the error until the field is valid or the user submitted.
Beta Was this translation helpful? Give feedback.
All reactions