Jake Howard

I fear then you can't use `react-native-mock` for integration testing, as we mock out the network-calling parts of the app, so you couldn't do any real API calls with it.

The driver was someone submitted a PR (#119). I've never done integration tests, so i'd consider network requests unnecessary for `react-native-mock`, but clearly there's a market for it. I believe...

I have been thinking on a nice way of implementing these fixes. I think the best way of doing it would be in the same way we override nodes require...

I am hoping to start work on something like this soon, once a few more PRs are released. Hoping to bring it out inline with react-native 0.30 so we can...

Nice. Can you implement it in the same way `TabBarIOS` is though, to keep the implementation the same as the rest of the library.

hmm, weird it doesnt like that, but i'm still not entirely happy with this implementation. Could you maybe add the 'Item' component as a static attribute of the `PickerIOS`?

I'm not a big fan of having an issue created for every release of react-native. As we'd probably end up many versions behind. I am liking the idea of having...

@rlau1115 Looks like some kind of problem in the code of exponent. The mock for `navigator` exposes that scene config properly. Whilst trying to use `react-native-router-flux`, I gave up trying...

@sibeliusseraphini Unfortunately the code I used is closed source by my company. I think that's more an issue for the `react-native-router-flux` repo, as it doesnt affect `react-native-mock`

Youre not setting up mockery correctly, the path is the path it imports not the path to the file. Please see mockery docs