From fecfa1f4b2d580bac7f27768c8d5cffd8c6b0ea7 Mon Sep 17 00:00:00 2001 From: Krzysztof Magiera Date: Wed, 12 Sep 2018 16:52:14 +0200 Subject: [PATCH] Update README.md --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a690dd24..c611dd97 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ This project aims to expose native navigation container components to React Nati ## Usage with [react-navigation](https://github.com/react-navigation/react-navigation) -Screens support is currently built into [stack navigator](https://reactnavigation.org/docs/en/stack-navigator.html). We plan on adding it to other navigators in near future. +Screens support is built into [stack navigator](https://reactnavigation.org/docs/en/stack-navigator.html) starting from version [2.14.0](https://github.com/react-navigation/react-navigation/releases/tag/2.14.0) of [react-navigation](https://github.com/react-navigation/react-navigation). We plan on adding it to other navigators in near future. To enable stack navigator to use screens instead of plain RN Views for rendering stack cards follow the steps below: @@ -29,8 +29,9 @@ useScreens(); Note that the above code need to execute before first render of a navigation screen. You can check Example's app [App.js](https://github.com/kmagiera/react-native-screens/blob/master/Example/App.js#L16) file as a reference. +4. Make sure that the version of (react-navigation)[https://github.com/react-navigation/react-navigation] you are using is 2.14.0 or higher -4. You are all set 🎉 – when screens are enabled in your application code react-navigation will automatically use them instead of relying on plain React Native Views. +5. You are all set 🎉 – when screens are enabled in your application code react-navigation will automatically use them instead of relying on plain React Native Views. ## Guide for navigation library authors