-
Notifications
You must be signed in to change notification settings - Fork 22
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
Confusion about shared screens/modals #7
Comments
Here's a demo using react-navigation RPReplay_Final1706020633_compressed.mp4 |
Okay, made some good progress actually, what I shared above seems to work okay, just making sure the href's are correct is quite the challenge! However I cant get the infinite pushing of screens like on the demo, it seems to just flash back to a previously mounted version? |
Yeah it seems something with my current setup wont allow me to keep pushing the same screen to the stack, it seems to go back to a previous version and also removes all previous screens from the stack as well? |
@JClackett were you able to solve this? |
not yet, here's an open issue: expo/expo#27183 |
Hello!
Thanks for the great template, im trying to switch my app over to expo-router but its significantly more complicated than this one obviously so theres a load of edge cases/scenarios that aren't super obvious how to handle. I have a load of shared screens/modals that can be opened from anywhere from the app's tabs and nested screens.
I'm struggling to understand where the modals should go and how to make them open as proper iOS "modal"s. Should they placed at the very top level outside the tabs layout? but then when closing it how do I know which tab to go back to? should I pass a "redirect" param?
Maybe easier to show my current structure and intentions, really struggling to see how I should structure these shared screens, with the below navigating around seems like it unmounts everything. Whereas on the old react-navigation I could keep pushing these screens and go back and forth indefinitely.
The text was updated successfully, but these errors were encountered: