You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah, indeed it looks like DOMException.name is being indexed already as error.type. Although, It's not shown on the error details page, in contrast to DOMException.code.
@behnam-oneschema right. We are setting code as a tag on the event. This is why it shows up in that heatmap on the issues page.
Having this as a tag makes very little sense, as all the errors that are grouped together likely have the same tag value. We should some sort of context instead probably. (Side-note: having type as a tag would equally not make any sense for the same reason)
@AbhiPrasad I think the TODO for us here is to move this into a context or data field.
Problem Statement
DOMException.code
is a deprecated feature. Reference: https://developer.mozilla.org/en-US/docs/Web/API/DOMExceptionThe codes are also hardly practical, considering only the numeric value of them is shown in the Sentry UI:
Solution Brainstorm
DOMException.name is the current best-practice in identifying these errors, and is supported widely across browsers:
The text was updated successfully, but these errors were encountered: