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
Search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue.
Bugs with react-navigation must be reproducible without any external libraries that operate on it. This means that if you are attempting to use Redux or MobX with it and you think you have found a bug, you must be able to reproduce it without Redux or MobX in this report. Redux related issues belong in react-navigation-redux-helpers, and we do not have any first-class integration with MobX at the moment.
Current Behavior
What code are you running and what is happening?
I'm trying to bind action creators to the navigation property. I am managing navigation state with redux.
I would expect my action creators from ActionCreators to be bound to the navigation property, however they are not. The idea would be to use navigation.someNavigationActionCreator() as opposed to binding navigation-related action creators to the AppNavigator Component itself (in which case I would be following the typical action creator flow of just calling someNavigationActionCreator().
I'm attempting this because I would prefer to follow the pattern of not explicitly using dispatch in my containers, which is how the documented example here is doing it: https://reactnavigation.org/docs/redux-integration.html
Is there not support for binding navigation-related action creators directly to the navigation prop?
Include a screenshot if it makes sense.
How to reproduce
You must provide a way to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repoistory as that is outside of the scope of Rect Navigation.
Either re-create the bug on Snack or link to a GitHub repository with code that reproduces the bug.
Explain how to run the example app and any steps that we need to take to reproduce the issue from the example app.
Your Environment
software
version
react-navigation
react-native
node
npm or yarn
The text was updated successfully, but these errors were encountered:
The issue tracker is reserved for bug reports only.
If you have a question, feature request, or an idea for improving the library or its related tools, please try one of the following resources:
Bugs with react-navigation must be reproducible without any external libraries that operate on it. This means that if you are attempting to use Redux or MobX with it and you think you have found a bug, you must be able to reproduce it without Redux or MobX in this report. Redux related issues belong in react-navigation-redux-helpers, and we do not have any first-class integration with MobX at the moment.
Current Behavior
I'm trying to bind action creators to the navigation property. I am managing navigation state with redux.
Expected Behavior
When doing this:
<AppNavigator navigation={addNavigationHelpers({ dispatch, state: nav, addListener, ...bindActionCreators(ActionCreators, dispatch), })} />
I would expect my action creators from
ActionCreators
to be bound to the navigation property, however they are not. The idea would be to usenavigation.someNavigationActionCreator()
as opposed to binding navigation-related action creators to the AppNavigator Component itself (in which case I would be following the typical action creator flow of just callingsomeNavigationActionCreator()
.I'm attempting this because I would prefer to follow the pattern of not explicitly using dispatch in my containers, which is how the documented example here is doing it: https://reactnavigation.org/docs/redux-integration.html
Is there not support for binding navigation-related action creators directly to the navigation prop?
How to reproduce
Your Environment
The text was updated successfully, but these errors were encountered: