Routing and navigation for your React Native apps
Bot releases are visible (Hide)
Published by satya164 11 months ago
Note: Version bump only for package @react-navigation/devtools
Published by satya164 11 months ago
Note: Version bump only for package @react-navigation/core
Published by satya164 11 months ago
Published by satya164 11 months ago
Published by satya164 11 months ago
Published by satya164 11 months ago
Published by satya164 11 months ago
Note: Version bump only for package @react-navigation/routers
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Note: Version bump only for package @react-navigation/devtools
Published by osdnk 11 months ago
cannot resolve use-latest-callback (#11696) (361bc6a) - by @jkaveri
onReady not getting called on native (#11628) (67232f1) - by @osdnk
fix!: don't use screen from params as initialRouteName (#11680) (4b681a9), closes #11680 - by @satya164
useUnhandledLinking
for handling deep links behind auth etc. (#11602) (688c43a), closes #10939 - by @osdnkinitialRouteName
.e.g.
navigation.navigate('MyScreen', { screen: 'NestedScreen' });
Here, the 'NestedScreen'
will be set as initialRouteName
.
It has the result of rendering the navigator with that screen as focused
screen. While this behaviour is expected, that screen was also used as
the initialRouteName
for every other operation ignoring the
initialRouteName
prop - which is not expected.
This change refactors the way the focused screen for initial render is
set to avoid this behavior.
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Published by osdnk 11 months ago
Note: Version bump only for package @react-navigation/routers
Published by satya164 12 months ago