Closed andrewhartwig closed 5 years ago
Okay upon doing even further digging, it almost seems like I don't need to be using this library, since I've already written most of the code that this library provides. I guess what I need to know, is what needs to be in the navigation
object?
I’d recommend just reading the source of this library. There is a utility function in core that will build a navigation
object for you.
@andrewhartwig Hello, i wanted to know if you were able to fix your Redux integration issues. since I'm having one myself and am struggling with it. https://github.com/react-navigation/redux-helpers/issues/97
Hello there! =)
I have an old react-native app that I am attempting to upgrade. Unfortunately, I have really tightly coupled my entire app with the redux-integration of react-navigation. Now it appears all those helpers are gone, and so I am left with integrating with this library!
So far the transition has been painless, but I am struggling with one last concept here.
src/reducers.js
src/AppNavigator.js
src/MainScreen.js
(nested Tab Navigation)Problem:
My confusion lies with this middleware here, originally there was no middleware for the navigator (Not sure how it worked before).
Your code snippet:
To my understanding, this tells react navigation which state to look at to trigger the page transitions.
How do I connect two separate navigators? Do I just need to have multiple middlewares?
This was my original code that provided said functionality:
I can't seem to figure out from your example where you would get the
navigation
prop from:Your example:
Any additional code requested can easily be provided. Let me know if there are any ways I can get my app running the way that it once did :)
Thanks, -Andrew