Daniel Friesen

> Write an optional plugin that will warn you about coding mistakes that work on web but will break React Native. For example, when {width: '24px'} is written emit a...

@kof They are billed at about 90% as just a subset of css styles. The 10% being a custom `aspectRatio`, `elevation` for Android, maybe some quirks in the flexbox implementation...

As a sample, here are the `src/List/ListItem.js` styles from Material UI annotated with how they relate to React Native: - red lines are only relevant to the browser - green...

The overlay doesn't hardcode the location of the game. It asks SteamVR what process is currently rendering to VR and if that appears to be the `EliteDangerous32/54.exe` process then it...

I'm not clear on what is happening. What do you mean by the overlay indicated you have manipulated the controls and by you keep getting prompts for keyboard input?

Same issue here. This package shouldn't be depending on moment with a `~` semver restriction, that's far too restrictive and even without this error would break this library since the...

I use this pattern all the time in React Native (babel + browserify) so this error is definitely related to some interaction with TypeScript compiler.

I think fromRenderProps should be usable for handling context. That said the lack of attention paid to the new context system is really disappointing. Especially given the fact that the...

> IMO should function the same as — this isn’t destructuring, and there really isn’t a reason as far as I can see to disallow this. It has no analog,...

How about using Symbols and supporting ES2015 computed property names (facebook/jsx#108). ```jsx ``` Essentially just desugars to: ```jsx React.createElement(Foo, {[React.key]: "foo", [React.ref]: callback, prop: "hi"}); ```