-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
mode prop for Screen #232
Comments
Feel free to send a PR moving We also need to deprecate
Why do you need it to be a function? |
If But I think the first option is more sensible |
I haven't done this in the past because it causes some visual issue in comparison to navigator nesting. Here's an example. Say I have a stack with a modal on top of a card. When the modal animates back to he card, the modal looks fine but the card still has the card movement, which means it is slightly offscreen to the left, and as the modal dismisses it moves back to the center of screen. The issue is fixable, but we need to be careful as we make big changes to CardStack, which is arguably the most complicated part of the codebase. |
I have a workaround for this https://github.com/nihgwu/react-native-dva-starter#advance, but this will introduce nested navigator issues |
Is this actively being worked on? |
For now, you can use this hack to easily support both types of screen inside of one navigator: It would be a huge change to add this feature as a navigation option, and we are trying to stabilize for v1. @nihgwu, if you have an idea for a simple implementation that doesn't cause lots of regressions, feel free to open a new issue and tag me. |
Right now
mode
is only available forStackNavigatorConfig
and only accepts a string, so all theScreen
s in it are with the same transition mode, if we want different modes between views, we need to define differentNavigators
and nest them, which makes things complex, so I have the following propose:mode
toScreen Navigation Options
mode
accepts a functionAny ideas? I'd love to send a PR to implement
The text was updated successfully, but these errors were encountered: