-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Issue with calling action when migrating from Redux Form v5.3.3 to v6.1.1 #2013
Comments
I didn't analyze all of the code, but the first thing I see that can be problematic is in the component and
As you can see in the docs (http://redux-form.com/6.1.1/docs/api/ReduxForm.md/), as of now,
And then you can dispatch Let me know if that helps. |
@iyn I use your approach on redux-form 6.7 version and react-boilerplate, I got an error |
Closing with bulk close of v5 issues. If this issue still requires action and/or also affects v6/7, please request a reopen with details or raise a new issue. v5 PR's are still welcomed. |
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. |
Hi Everyone,
I can't seem to figure out why my action is not being called when I migrated my version 5 redux form to v6. Currently, action is being called but nothing is being returned and no dispatch is sent to reducer at the moment. I am using redux thunk as a reducer, but my action never gets dispatched to the reducer when I make the switch. V5 version redux-form works perfectly. Below is my action/action creator, V5 and v6 form components.
I am pointing out in line 8 of the action where the function stops returning results.
using version 6.1.1 and migrating from 5.3.3.
I need to migrate because of the improvement in deep forms in version 6 has drastically improved my other parts of the app but I can't get this seemingly simple Sign In component to work...
Thanks!
ACTION
VERSION 6.1.1 REDUX FORM COMPONENT
VERSION 5.3.3 REDUX FORM COMPONENT
The text was updated successfully, but these errors were encountered: