Releases: grahammendick/navigation
Releases · grahammendick/navigation
NavigationReactNative v5.1.0
NavigationReactMobile v3.0.0
Change
- #248 Reverted allowing each Scene their own React Root now that Native is a single Root
NavigationReactNative v5.0.0
Thanks @jacobp100 for suggesting the move to a single React root and for an example iOS implementation
New
- #246 Added Search Bar Component on iOS
Fixed
- #245 Rendered scene before pushing so don’t get a blank screen during transition
- #245 Showed UI Bar Buttons on iOS immediately instead of waiting for transition to complete
- #245 Ensured navigating back 3 or more crumbs on Android returns to the correct scene
Changed
- #245 Removed Android and iOS-specific setup
- #245 Rendered all scenes under a single React root (see the new
NavigationStack
andTabBarIOS
components) - #245 Configured iOS titles, Android custom animation and shared element transitions via props on the
NavigationStack
Migration
Because there’s no longer any native setup required, revert the setup changes made to AndroidManifest.xml
(Android), and AppDelegate.h
and AppDelegate.m
(iOS). Consult the updated setup guide for the JavaScript differences.
Navigation v5.1.1
Fix
- #244 Improved the performance of fluent navigation link creation
NavigationReact v4.1.0
New
- #244 Added
FluentLink
component for declarative fluent navigation
NavigationReactMobile v2.1.0
New
- #243 Allowed each Scene their own React Root to match Native
NavigationReactNative v4.0.1
NavigationReactNative v4.0.0
Fixed
- #231 Updated stale scene when peeking on iOS, e.g., fluently navigating from A → B → C to A → D → C
Changed
- #231 Added
tab
prop toScene
component, mandatory when using the iOS tabs setup - #232 Accessed iOS title from
getTitle
function onState
instead of readingsceneTitle
from navigation data. You can use the following to revert to the previous iOS title behaviour:
for(var key in stateNavigator.states) {
var state = stateNavigator.states[key];
state.getTitle(({ sceneTitle }) => sceneTitle;
}
- #232 Accessed Android shared elements from
getSharedElements
function onState
instead of readingsharedElements
from navigation data. You can use the following to revert to the previous Android shared elements behaviour:
for(var key in stateNavigator.states) {
var state = stateNavigator.states[key];
state.getSharedElements(({ sharedElements }) => sharedElements;
}
NavigationReactNative v3.7.0
New
- #227 Retrieved Shared Elements from function attached to
State
(Android)
NavigationReactMobile v2.0.1
Fixed
- a187304 Ensured the Shared Element navigation comes to rest