fix: add missing react-navigation props#511
Merged
thiagobrez merged 1 commit intomainfrom Apr 14, 2026
Merged
Conversation
satya164
approved these changes
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Description
Props
screenLayout,UNSTABLE_routeNamesChangeBehaviorandUNSTABLE_routerwere not passed down to the react-navigation builder, so they couldn't be used in the navigator.This PR bumps the react-navigation versions and passes down these props so they can be used in the NativeBottomTabNavigator.
Example:
How to test?
Added a new example route in the test app:
"Native Bottom Tabs with screenLayout"Open the example route and notice the layout common to all tabs. Change tabs and notice the route name changing in the common layout.
Screenshots