From 91cb2bd423c3dd9f2ca52cda393b68459319db03 Mon Sep 17 00:00:00 2001 From: Krzysztof Magiera Date: Tue, 25 Sep 2018 09:26:01 +0200 Subject: [PATCH] Update README.md --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index c7b08f83..76fecb0e 100644 --- a/README.md +++ b/README.md @@ -56,6 +56,15 @@ useScreens(); 3. That's all 🎉 – enojy faster navigation in your Expo app. Keep in mind screens are in pretty early phase so please report if you discover some issues. +## Interop with [react-native-navigation](https://github.com/wix/react-native-navigation) + +React-native-navigation library already uses native containers for rendering navigation scenes so wrapping these scenes with `` or `` component does not provide any benefits. Yet if you would like to build a component that uses screens primitives under the hood (for example a view pager component) it is safe to use `` and `` components for that as these work out of the box when rendered on react-native-navigation scenes. + +## Interop with other libraries + +This library should work out of the box with all existing react-native libraries. If you expirience problems with interoperability please [report an issue](https://github.com/kmagiera/react-native-screens/issues). + + ## Guide for navigation library authors If you are building navigation library you may want to use react-native-screens to have a control which parts of the react component tree are attached to the native view hierarchy.