>Can probably compile a list of high profile libraries that suck if anyone is interested
Please do!
I agree with your stance on react-native navigation, but I'm not having too many problems with react-navigation. What's your issue with it?
Please do!
I agree with your stance on react-native navigation, but I'm not having too many problems with react-navigation. What's your issue with it?
react-navigation is pretty good actually, haven't had any big issues this time. At the beginning when I first evaluated it they had breaking changes way too often, things were buggy, all in all, it wasn't ready for production. Today it feels different, but I can't write a blog post about it yet as I haven't been using it for long enough.
I'm still not sure how to get previous functionality from 2.0 (app wide background image) working in 3.0, considering that now my root component has to be provided by React-Navigation.
<ImageBackground> <RootNavigator/> </ImageBackground>
There can be only 1 navigator rendered at a time, but it does not have to be the root of your application. Otherwise there wouldn't be any redux, either.