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
Initially, I am in the SimpleStack in Screen1. I navigate to Screen2, then Screen 3, then over to Drawer/Drawer1 which is displayed modally. When I dispatch the NavigationActions.back() action, the modal view is popped and I land back on SimpleStack/Screen3. The problem here is I'd really like to be able to land back on SimpleStack/Screen2.
To tackle this problem, I think it would be nice to mirror the navigate API and be able to something like this, in my case, from Drawer/Drawer1:
In this case, I think you can dispatch several actions at once, and the correct thing will happen. Or, after we merge #3393, you can go back by providing a key on the navigate action, which allows you to navigate back to the specified screen.
Feel free to open a new issue if that doesn't work.
I have the following Navigator setup (simplified):
Here is what I am trying to accomplish:
Initially, I am in the SimpleStack in Screen1. I navigate to Screen2, then Screen 3, then over to Drawer/Drawer1 which is displayed modally. When I dispatch the
NavigationActions.back()
action, the modal view is popped and I land back on SimpleStack/Screen3. The problem here is I'd really like to be able to land back on SimpleStack/Screen2.To tackle this problem, I think it would be nice to mirror the
navigate
API and be able to something like this, in my case, from Drawer/Drawer1:Does this line of thinking make sense? Is there an alternative here that I am missing?
The text was updated successfully, but these errors were encountered: