Stephane Rufer

Results 6 comments of Stephane Rufer

@gaearon Is this a good approach to using prop-types checking outside of React? Or is there a better way?

The PR has been updated to not throw an error, but instead calls the function passed in as an argument, with the same arguments as are passed to `warning`.

I'm aware that there might not be time to review this PR, but with React 16 in beta now the resolution on how to use prop-types with custom errors is...

This still seems to be an issue. Is there a workaround?