-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[V2][IOS] Resolve 'push'-command with next componentId for ios #4229
[V2][IOS] Resolve 'push'-command with next componentId for ios #4229
Conversation
Good catch! |
Can you also fix the return type of |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
…oot' command interface
Sorry for long inactivity. |
Hey! This really needs to be merged! |
I created a new, conflict-free, PR: #6445 |
This was addressed in #6422 and has been released in v7. |
Behavior of
Navigation.push(someComponentId, layout)
between android and ios is different.In android promise resolves with next componentId (id of component that was pushed), but on ios - componentId on which we pushed.
Android: https://github.com/wix/react-native-navigation/blob/v2/lib/android/app/src/main/java/com/reactnativenavigation/viewcontrollers/stack/StackController.java#L145
Motivation of this PR - keep api behavior more consistent.