3 ms·
>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
by stackola 8y ago
>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?
- ponyous 8y agoSeems like there is interest, will compile and publish to HN in the next couple of weeks. 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.
- com2kid 8y ago3.0 has some breaking changes, but hey, they are using semver correctly at least! 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.
- stackola 8y agoYou can wrap your root navigator! <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.
- com2kid 8y agoAh ok, the docs didn't make it 100% clear and I got tired messing with the toy app I was using with React Navigation.
- java_script 8y agoPeople already do this, they're those "awesome-react", "awesome-redux", etc GitHub repos with the giant readmes and peppered with emojis. IMO it's kinda mean to sarcastically name them like that.