Releases: vonovak/react-navigation-props-mapper
Releases · vonovak/react-navigation-props-mapper
v3.1.0
What's Changed
- Bump shelljs from 0.8.4 to 0.8.5 in /example by @dependabot in #46
- Bump nanoid from 3.1.30 to 3.2.0 by @dependabot in #48
- Bump nanoid from 3.1.30 to 3.2.0 in /example by @dependabot in #49
- Bump follow-redirects from 1.14.5 to 1.14.7 in /example by @dependabot in #47
- Bump follow-redirects from 1.14.7 to 1.14.8 in /example by @dependabot in #50
- feat: allow usage of wrapped components outside of navigator by @vonovak in #52
Full Changelog: v3.0.0...v3.1.0
Release 3.0.0
v1.0.4
v2.0.0
This version supports react-navigation
v5 and drops support for older versions.
If you've used this library with previous versions of react-navigation
, this means you can forget about two steps of the v5 migration process! 🎉 See separate route prop and no more getParam.
Breaking
- navigation props are passed from
props.route.params
now instead ofprops.navigation.state.params
(this has changed inreact-navigation
v5) screenProps
were removed fromreact-navigation
v5 so we do not pass them throughstatic navigationOptions
were removed fromreact-navigation
v5 so we do not support this either
v1.0.2
v1.0.1
v1.0.0
❌ Breaking
The module now exports a single function: withMappedNavigationParams
. It replaces
withMappedNavigationAndConfigProps
available previously:
withMappedNavigationParams
will map navigation params passed to your screen component, and if you use static navigationOptions
function, it will also map the params passed into that function. The same thing, but a better name.
🎉 New features
- flow typings are included
- the distributed code is compiled with Babel, which will make usage in Jest tests a little easier (no need to tell Jest to transform the module)
- new
wrappedComponent
property to get the original component wrapped bywithMappedNavigationParams()
(see readme or tests)