* 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
* [ReduxExample] Delete android and ios dirs
* [ReduxExample] Upgrade using create-react-native-app
* [ReduxExample] Add postinstall script to clean up files Yarn copies in
Yarn copies them when installing locally, causing lots of @proviesModule collisions.
* [ReduxExample] Upgrade expo and other dependencies
* [ReduxExample] Don't delete .git just in case
* [Playground] Commit auto-changes to package.json, yarn.lock
* [Playground] Rerun create-react-native-app
Preserving rn-cli.js and transformer.js
Still not quite working.
* [Playground] Fix the Expo loading issue by removing projectRoots
Now it looks in the right place to find its resources, including 'entryPoint'.
* [Playground] Add postinstall script to clean up files Yarn copies in
Yarn copies them when installing locally, causing lots of @providesModule collisions.
* Update the Contributors guide to explain how to use the example app
And recommend Yarn by default
* [Playground] Remove now-obsolete rn-cli.config.js
* [Playground] Upgrade expo and other dependencies
* [Playground] Don't delete .git just in case
* Update Stacks{In,Over}Tabs example for better clarity
* Remove redundant navigationOptions in stack examples
* Update text in ReduxExample to clarify which route is being used
* [ReduxExample] Programmatically generate initial state
* [ReduxExample] Return original state if nextState is null
* [Docs] Add getStateForAction to redux integration example
* [Docs] Add link to ReduxExample app
* [Docs] Give each example a 'DRY' README linking to real docs
* [Docs] Clean up the Contributors guide a bit
* [Docs] Remove numbers from sections in Contributors guide
They don't seem very meaningful, and don't need to be done in order
* [Example] Get tests passing on ReduxExample and NavigationPlayground
* [CI] Use more vague versioning so we're always up to date
* [CI] Test that the example apps run without error
* [CI] Install the current local version of react-nav before testing
* Fix tabs => spaces in ReduxExample/package.json
* Remove LinkingExample entirely
It's now part of NavigationPlayground.
* [Example] Upgrade dependencies to fix the ReduxExample app
* [Example] Also upgrade and fix the LinkingExample app
* [Example] Update MainApplication.java to fix Android API
* Initial commit
* Remove HybridExample (#985)
* Remove HybridExample
* Remove last mention of HelloHybrid
* Remove console log
* Fix flow and example
* Fix routers api docs
* Keep options in single place
* chore
* Fix styling
* Organise miscs
* Better flow type for screen options
* Flow test website and add more types to options
* navigationOptions instead of prevOptions makes more sense
* Fixes
* Fix up docs
* Fix
* Update route decl
* Provide error when removed API is used
* Remove lock
* Add validators
* Make StacksOverTabs config valid again
* Do not return
* Fix redbox
* [Example] Fix the ReduxExample app
Just a bit of cleanup so it can run.
* [Example] Remove AsyncStorage persistence from ReduxExample
It's a cool feature, but isn't necessary to demonstrate how to use
react-navigation and may cause more confusion than it's worth.
* [Playground] Duplicate StacksInTabs to StacksOverTabs
* [Playground] Move nested routes into root stack so they appear on top
* [Playground] Go to SettingsTab instead of pushing a new Settings screen
* [Redux example] Use HTTPS-enabled endpoint to get npm modules
To fix 'yarn install'
* [Redux example] Add ReduxExample to rn-cli.config.js
This prevents those annoying @providesModule naming collisions
* [Examples] Add a basic README linking to the usage instructions
