Replies: 1 comment 3 replies
|
Since component stack uses the same management system as blank stack, I figured the best way of handling both was through flags (DISABLE NATIVE SCREENS). Originally the idea for component stack was to have it be used for embedded scenarios but blank stack could easily do this with native screens so in the next major version component stack and that annoying flag will probably be removed. Edit: |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Was using the flag
DISABLE_NATIVE_SCREENSin blank stack, however it always used a native screen. I looked at the source and it seems to intentionally? override that so the prop never works.https://github.com/eds2002/react-native-screen-transitions/blob/e8eb6fd13ddaf1b03272518ca6d2f117b6f7f9fb/packages/react-native-screen-transitions/src/shared/providers/stack/core.provider.tsx#L73C3-L79C5
Can I PR it to change the order? I do not want to use a native screen when using blank stack.
All reactions