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
[Feature Request] Include 'submitting' and 'submitSucceeded' in the selectors #2173
Comments
@erikras Also I see that one can't access field level errors within the form. I'm curious for the reasoning there - does it make too prescriptive that the error has to be accessed/displayed alongside the field? Alternatively, is that something you could see be one of the selector? |
Normally - you should have selectors |
Fix published in |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
To implement a solution discussed in #2169 (@erikras's 'Many little forms' solution) cleanly, I need to manage logic in the parent container based on whether each of the little forms (auto-saving each field) are submitting or have submitted, etc.
Looking through the documentation in the API, it seems that while one can check for errors or state of a field, there is no selector giving access to see if form is
submitting
, hassubmitSucceeded
orsubmitFailed
.In simple cases, one can access the state directly through custom selectors. But for sake of consistency as well as for more complex cases, it might be worthwhile having the following selectors:
isSubmitting
: Corresponds to thesubmitting
prop.hasSubmitSucceeded
: Corresponds to thesubmitSucceeded
prop.hasSubmitFailed
: Corresponds to thesubmitFailed
prop.Not sure if there are more complex reasons for not having those selectors, but I would love to understand more!
The text was updated successfully, but these errors were encountered: