5 Commits

Author	SHA1	Message	Date
Satyajit Sahoo	8b11e4df0c	chore: reuse the stack code from react navigation 5 ... The code for the stack is almost the same as v5, with the only differences being the types and the navigation object. To avoid making same changes in 2 places which error-prone, I decided to reuse the same code. Due to the differences, it's not possible to just use it as a dependency, so I followed this approach: - Copy the source files on post install and apply patches to make it work with React Navigation 4 - When we need to make changes, we can make them in v5 repo and update the version here, most of the time it wouldn't need any extra work - If we need to make v4 specific changes, we can change the code in vendor/ and then re-generate the patch with `yarn patch`	2019-12-10 15:22:12 +01:00
Brent Vatne	4d0a1a5178	feat: switch to react-native-safe-area-context	2019-08-29 16:38:43 -07:00
satyajit.happy	ca432e0354	chore: update expo-cli and eslint	2019-10-05 22:56:42 +02:00
satyajit.happy	4c012ad1ea	fix: add peer dep on react-navigation	2019-09-09 21:52:09 +02:00
satyajit.happy	dee470829a	chore: configure bob and metro	2019-04-17 14:47:03 +02:00