feat(exception-group): Display related exceptions in UI

[malwilley]

Closes #47085

[mattjohnsonpint]

Looking good so far, thanks! We'll have to wait until https://github.com/getsentry/team-ingest/issues/102 is complete, or at least until getsentry/relay#2020 is deployed. It's already merged and staged for next release of Relay. You could set up a local Relay instance to test with in the meantime, if that would be helpful. But I think it will be easier to collaborate on UI changes when it's deployed to sentry.io.

[malwilley]

@priscilawebdev since you have the most experience with the stacktrace components could I bother you for a review?

There is a .NET issue in the sentry-sdks org you can test with here

[priscilawebdev]

do we want to merge this PR that is not behind a feature flag even if the task is not completed yet?

[priscilawebdev]

should we add a description next to the links so users can know which exception group it belongs to?

Example:

- System.AggregateException
   . System.Exception - Test 1
   . System.Exception - Test 2

[priscilawebdev]

when jumping to a group of exceptions, shall the frames be expanded by default?

[priscilawebdev]

I am confused by this, since the first exception matches the description but it is not collapsed by default

[priscilawebdev]

will this new change also be applied to threads? it would be nice to have a few examples

[priscilawebdev]

nit: noticed that we don't have a spacing between the description and the tag on smaller devices. can we please add some?

[priscilawebdev]

tested the example exception and many others (nextjs, javascript, python, flask) and the UI looks good to me. will only wait for a few answers to my questions before approving 😉

[malwilley]

Thank you for the thorough review @priscilawebdev! I've pushed commits that should address all your comments, and answered your questions below:

do we want to merge this PR that is not behind a feature flag even if the https://github.com/getsentry/team-ingest/issues/102 is not completed yet?

There shouldn't be any risk to merging this without a feature flag since this will only apply to issues with exception groups.

should we add a description next to the links so users can know which exception group it belongs to?

Yes! Added here: a13209e

am confused by this, since the first exception matches the description but it is not collapsed by default

Ah yes, collapsing child exception groups will be done in a followup ticket

will this new change also be applied to threads? it would be nice to have a few examples

Exception groups are only implemented for the Exception interface, so this won't be a feature of threads (for now).

nit: noticed that we don't have a spacing between the description and the tag on smaller devices. can we please add some?

Good catch, I'll fix that in another PR since that shouldn't be related to these changes

[priscilawebdev]

🚀