6f4075f38e
When subclassing a JS error, most browsers include the constructor stacktrace :/ This is an issue, because: - The stacktrace is deeper than it should be - The stacktrace reaches into a polyfill for which there is not source map, which causes Sentry to infer the issue grouping from the JS file name. And the fingerprinted name changes on each release. So for each release, the stacktrace is different ; and Sentry can't group issues properly. |
||
|---|---|---|
| .. | ||
| components | ||
| loaders | ||
| manager/fields | ||
| new_design | ||
| packs | ||
| shared | ||