15 Commits

Author SHA1 Message Date
Dave Pack
c4541f44af Updates examples to react-native 0.48.4 and expo sdk 21. (#2675) 2017-09-29 16:06:56 -05:00
Ashoat Tevosyan
b759d3136e Fix Flow types (and update RN version) (#2619)
* 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
2017-09-25 11:29:34 -05:00
Kevin Cooper
19babadf38 Fix the NavigationPlayground example! (#2170)
* [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
2017-09-06 10:36:20 -05:00
Adam Miskiewicz
e2afc982da
Fix tests in NavigationPlayground 2017-07-19 14:03:58 -07:00
Adam Miskiewicz
ebf1e2e893
Update NavigationPlayground to 0.45.1, add stub react-nav flow definition 2017-07-19 12:59:40 -07:00
Adam Miskiewicz
83e2cf007b
Fix tests in examples 2017-05-15 19:36:04 -07:00
Adam Miskiewicz
518f491727
Install react-navigation in NavigationPlayground 2017-05-15 19:12:52 -07:00
Adam Miskiewicz
1cd16bcf4a
Convert NavigationPlayground project to a CRNA project 2017-05-15 18:57:22 -07:00
Adam Miskiewicz
fe9e30d8a8 Change react-navigation path in example package.json to relative 2017-05-14 21:28:38 -07:00
Adam Miskiewicz
1ae3798137 Upgrade to React Native 0.44 + Flow 0.42 2017-05-14 21:28:38 -07:00
Kevin Cooper
85c2235a3c Improve CircleCI infrastructure (#1173)
* [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.
2017-04-24 10:54:58 -07:00
Joe McKie
2bbfc03cd0 Bump dependency versions to reflect current RN 2017-04-18 15:04:47 +02:00
Mike Grabowski
ce5be229ed Upgrade React Native (#1093)
* Upgrade RN

* Clean up
2017-04-18 14:28:47 +02:00
Mike Grabowski
93976d358e Introducing flat options (#984)
* 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
2017-04-12 15:49:08 -07:00
Adam Miskiewicz
c37ad8a0a9 Initial public release of React Navigation 2017-01-26 11:53:33 -08:00