resourcesavingcontainer react-native-screens on stack on android and drawer for both ios and android (feature request)
fix drawer behaviors in various situations (eg: don't unmount when you switch away by default) (@brentvatne)
export a scrollview component that scrolls to top automatically when tapping tab icon and already at first screen in stack for that tab. it should also handle insets with translucent headers and tabbars. (@brentvatne)
figure out what to do about web now that we're adding rngh dependency to navigators
improve web support: experimental subrepo approach (@ericvicenti)
todo right before release
breaking change: manually wrap your app in navigation container (@ericvicenti)
better story around modals (full screen and partial overlays) (probably easier to implement after transitioner re-implementation) (note: WIP with transitioner and also incoming RFC for portal)
better safe area view (status bar translucent/opaque/varying height, safe areas, maybe keyboard?) (WIP primitive for safe areas in react-native)
make safe area view navigation-aware (translucent header)
integration tests that we can use for focus events (@ericvicenti)
hiding tabs from tabbar (feature request) - whether we implement this or not, understand what people want to do and explain how to achieve behavior in docs
goBack(null): be explicit about how it works, any design considerations when building your own router to place nicely. perhaps have a different name for the helper.
audit performance: be able to explain why we do each render on every re-render of a screen or header
The text was updated successfully, but these errors were encountered:
todo
resourcesavingcontainerreact-native-screens on stack on android and drawer for both ios and android (feature request)todo right before release
navigationOptions
on navigator config should correspond to the navigation options for that router. another key,defaultChildNavigationOptions
should do what the current one does. (from https://github.com/react-navigation/rfcs/blob/master/text/0005-shallow-navigation-options.md) (@brentvatne)wip but won't be ready or postponed for v4
The text was updated successfully, but these errors were encountered: