* Add Flow libdef
* Move libdef to flow folder in root
* Update libdef with some refinements discovered while writing test
Mostly refining navigator config types. In the past when we tried it we got in-repo Flow errors. With a libdef we can now assert it as true!
* Get rid of all imports in libdef and refine some types
* Fix .flowconfig to stop ignoring modules and properly include React Native libraries
Currently, there are numerous ignored libraries that are hiding type errors. Actually, they're causing type errors too. This sort of thing only patches over actual problems, so we have to revert them to get a config we can build upon.
* Update react-native/flow-bin dependencies
We want to have Flow types working with the latest packages.
* Update flow-typed libraries (auto-generated)
* Fix typing of navigation prop used by withNavigation HOC
The current typing is clearly a typo, as it is circular. `NavigationScreenProp` should be used to type the navigation prop
* Fix typing of easing function
What's funny is that I fixed this before in d71ed75133b97e33a8a683eda334b3005107d379. @skevy reintroduced the mistyped function in 9436d03fe8fface09001a5a40ce0aa8a01ad9e7e, which didn't trigger any Flow errors because .flowconfig was ignoring the entire react-native package
* Correct typing of View and Text style prop
The current code thinks it can import these, but this isn't true, and was being hidden because the .flowconfig ignored the whole react-native package. There's no easy to type Text and View at the current moment, as far as I can tell. Importing the highly generic `StyleObj` seems like the best bet, and is what I have being using in my projects.
* Import NavigationScreenComponent using full path
* Updating yarn.lock files
* Get rid of library overrides in flow-typed/react-native.js and flow/react-navigation.js
* Add @flow to src/react-navigation.js and make last three params to createNavigator optional
* Make screenProps and navigationOptions optional in NavigationNavigatorProps
* yarn run format
* Readd react-navigation/node_modules ignore to NavigationPlayground's .flowconfig
Realized this line I removed in the first commit is necessary when using npm link/yarn link, which is what the CircleCI build does
* Make all DrawerViewConfig's params optional
Some of these params are marked as optional because they have defaults. However, the only place `DrawerViewConfig` is used is as the input the function that then applies the defaults
* Make all props in NavigationNavigatorProps optional
`NavigationNavigatorProps` is used to type the props of the component that is output by the `StackNavigator`, `TabNavigator`, etc. component factories. This component does not need to have any props specified.
* Make second param to `DrawerNavigator` factory optional
`DrawerNavigator`, just like `TabNavigator` and `StackNavigator`, can be called with just a single argument (ie. omitting the config)
* Upgrade to RN 0.48.4 to address https://github.com/facebook/react-native/issues/15810
