We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Its a doubt rather than a issue , how the Logout action is handled in navigation reducer,
I checked code , where u reset using Navigation Action and again init with login routeName.
How does it work internally. i have usecase where
TabNavigator({ banner: {screen: banner}, login: {screen: login}, home: TabNav({ logout: { screen: logout }, eventListing: StackNav({ event: { screen: event } }) }) })
let say my im in Logout screen , how do i update stateForLoggedOut using NavigationAction reset.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Its a doubt rather than a issue , how the Logout action is handled in navigation reducer,
I checked code , where u reset using Navigation Action and again init with login routeName.
How does it work internally. i have usecase where
TabNavigator({
banner: {screen: banner},
login: {screen: login},
home: TabNav({
logout: { screen: logout },
eventListing: StackNav({
event: { screen: event }
})
})
})
let say my im in Logout screen , how do i update stateForLoggedOut using NavigationAction reset.
The text was updated successfully, but these errors were encountered: