the problem I see with many bug reports in this repo is that people write a very vague description of what their problem is and expect to get some help. I tried to:
1 . emphasise how important it is to include a runnable reproduction
2 . cut down on some extra words at the beginning of the template so it's more to the point
* 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
* added drawerLockMode with cabilities to update it on the fly
* fixed incorrect name on markdown for usage
* added handling if screenProps is not being used
* Fix linting error
* Use drawerLockMode instead of lockMode
* Correct docs
* Fix flow issues
* Make drawerLockMode optional
* Mock and verify console warnings to prevent noise in the test output.
* Tighten up expectations on deprecation output.
* 80 column formatting.
* Actually fix formatting.
* Ignore the jest setup file when calculating test coverage.
* Actually collect coverage from the whole library codebase so that the numbers are actually useful.
Previously, we were creating an anonymous function as the event listener handler. This means we can't un-listen because we don't have a reference to the handler.
* [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
* Update .eslintrc to allow compile.
* Resolve .web.js extension
* Look for __DEV__ on global
Fixes ReferenceError when not in the React Native environment.
* Replace __DEV__ at compile time via babel
* Don't try to lint a website build
* [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
Because react-native-tab-view insists on sticking at 0.0.*,
the caret version pinning won't install "minor" updates.
Semver rules are weird with 0. major versions.
Is this something you'd be interested in?
* Add additional guidance information to the GitHub issue template.
- Provides links to best places to ask usage questions.
- Uncomments guiding information in issue template that wasn't visible when creating issue.
- Based on questions asked here: https://new-issue.vuejs.org/#modal
* Remove ' instead of the expected behavior'
