Jake Howard

That's a very strange error, possibly an issue to do with proptypes? Are your components using the `number` proptype validator? Also, possibly unrelated, you seem to be using both `jest`,...

Documentation on support is unfortunately kinda lacking. I dont have support for any version of `jest`, as it has a builtin mock of `react-native`, however there's theoretically nothing stopping it...

Ah yes. If you would submit a PR that'd be great :grinning:

No, that's certainly something for this library. If you would like to open a PR on this it would be great!

Looking at the source, it appears it's a bug that's carried through from day 1. Seems it's trying to access a special prop that isnt there. Although, i'm not sure...

I believe that's something to do with how shallow doesnt render everything. Mount is definitely a better test of this library, although it is only designed to be used with...

That looks like an alright solution. Especially as it allows not only the types to be valid as with react-native (numbers as keys), but we can also work out the...

Ooh, that's a nice improvement. I'm kinda suprised proptype failures cause tests to fail though, but hey it is an actual error i guess. I plan to spend a large...

Looks like it's a near drop-in replacement for ``, should be nice and simple to implement from the `` mock

This issue would resolve itself if `react@16` would come out of alpha. But yes I agree that fixing the dependencies should fix the issue, however i'm not sure requiring ^16...