-
-
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
Help needed #768
Comments
Unfortunately, I don't have near the experience that I'd like to have with That's about all I can tell you without seeing (and running) your source code. |
Thank you Erik! If so, please let me know how I can get in touch with you. My email is on my github homepage, would you want to reach me. Thank you! |
I'm using react-router-redux and redux-form and haven't had any issues yet. Feel free to post a snippet of the form and maybe I can help |
Thank you, Jesse! I really appreciate you stepping forth. I've uploaded the code to https://github.com/jean-Phil/redux-form-navig-issue/, and put my goals and the bugs I encounter in the readme file. |
Hello Erik, Thank you for having a look already. The message part of state is not fully implemented yet. For now, I've pushed a new version, to solidify and clarify that part of the updateMessages fn. It did not seem to throw on my end. |
Okay, now I'm not seeing any exceptions. It's dispatching |
At this point, it is not navigating automatically back to the /list route. If you want to recreate navigation on your end, you must first clear away the "undefined" from the url, and a button will appear, allowing you to navigate to the other view.
|
So a few things. If you want to use the react-route-redux actions, you need to add the routerMiddleware. This allows the dispatched history actions to actually change the history
The actual actions you are trying to dispatch can just be grabbed directly from the react-router-redux module. For example, you can get the "push" action
And then dispatch it. For sake of debugging, try doing the simple case of transition without query or state
You do not need to reference the actual history object to dispatch the action with the newest version of react-router-redux. |
That did the trick, indeed! ... and now initialization and form destruction seem to work fine as well. |
You can 💀 it. Glad we could help. Happy coding! |
Glad to help and glad its working |
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. |
Hello Erik,
I apologize in advance: this should not be an issue, but a request for help, however I don't know how else to get in touch with you.
I've managed to build a simple two-page app ( list and form view ) which would do what I intended it to. However, I am experiencing difficulties with action calls having undesired effects, and I've really spent too much time trying to debug this... I've reached the stage where I need someone more experienced to look at my code and provide guidance...
Between @@router/LOCATION_CHANGE and redux-form/DESTROY action calls, I am getting 'Uncaught TypeError: Cannot read property 'type' of undefined' and I don't seem to be able to fix this. I've searched for similar issues eg. https://github.com/reactjs/react-router-redux/issues/182 but cannot wrap my head around the problem.
I am obviously more than willing to compensate you for your time. Please let me know if you could find time to help me solve this. I believe an hour may be sufficient.
Thank you in advance!
JP
The text was updated successfully, but these errors were encountered: