4 ms·
For what it's worth we have been vocal on the issue tracker about this for a long time: https://github.com/facebook/react/issues/2686 https://github.com/faceboo
by the_mitsuhiko 10y ago
For what it's worth we have been vocal on the issue tracker about this for a long time: https://github.com/facebook/react/issues/2686 https://github.com/facebook/react/issues/2686
- spicyj 10y agoI know. From @benvinegar's comments there (ex: https://github.com/facebook/react/issues/2686#issuecomment-217990488 https://github.com/facebook/react/issues/2686#issuecomment-2...) it sounded like the error code system would go at least most of the way towards solving your problem. Obviously the error message would not show up in Sentry automatically, but I figured that it would be a click away. I guess I must have misunderstood something along the line though.
- the_mitsuhiko 10y agoWe automatically resolve your error codes now. We just wish this was at least a standard like sourcemaps.
- bentlegen 10y agoIt's a huge step up and I'm grateful, not only because this will be a huge improvement for Sentry users (and other crash reporting service users), but also because we use React ourselves. Thanks React team.
- skrebbel 10y agoSome people will just never stop complaining. Thanks for your great work.