feat(ui): issue detail page with event list and status actions - #314
Merged
Conversation
- Add /issues/[issueId] page: metadata stats, resolve/ignore actions, paginated event list linking to event detail - Extract exception type/value summary from Sentry-format payloads - Extend e2e: event list navigation + resolve action coverage
ajianaz
force-pushed
the
feat/issue-detail-page
branch
from
September 3, 2026 05:19
b8c1e29 to
7a91728
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
/issues/[issueId]route: the issues list already linked here, but no page existed (SPA fallback rendered an empty shell)listEventsAPI), each row linking to the existing event detail page; exception type extracted from Sentry-format payloadsWhy
Issue detail is the core flow of an error tracker: rows linked to
/issues/<uuid>but the page did not exist.api.listEvents(issueId)was wired in the API client and backend but never used by any page.Testing
npm run check(0 errors),npm test(10/10),npm run buildpassnpx playwright test e2e/issues.spec.ts: 7/7 pass, verified stable across two consecutive runs against a live server