Gur Kohli
Gur Kohli
Hey, sure I will work on the fix and submit a PR soon. Thank you.
@johanbrandhorst I have a PR open in improbable-eng/js-browser-headers to fix this. Would you have or know someone with privileges to review it?
@johanbrandhorst We're blocked until this PR is merged, would you be able to push someone to review this considering it's the same organization or have some sort of ETA on...
Ah okay I understand. I guess we would have to look for alternate solutions if this PR doesn’t get merged soon. Thanks for all your help!
In this case yes, but the error shows up even if a rendered react component was passed as prop. My exact use case is such, we have a wrapper over...
That's a valid solution but I also think that, given how React and prop-types are commonly used in combination, and that the JSON.stringify here is for the purposes of error...
This would be very useful for our workflow as well. Would appreciate if this could get onto the roadmap