Repository navigation
feat(dashboard): Polish event details header and stack nested drawers - #2418
Merged
Merged
Conversation
Show a readable UTC timestamp and the event sequence number, and keep the step controls beside close so they do not move with the event type width. Co-Authored-By: adm <aditya.mathur@sentry.io>
… edge to edge Move the side Drawer to the shadcn Base UI drawer, so event details opened from a subagent drawer stack in front of it. Remove the body inset for the subagent event log, so rows meet the drawer edges and the sticky toolbar has no gap above it. Co-Authored-By: adm <aditya.mathur@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Join the previous and next event buttons in one shadcn button group, so they read as one control apart from close. Co-Authored-By: adm <aditya.mathur@sentry.io>
Match the data-[swipe-axis=x] variant of the drawer's 75% default, so the full-width override wins below 640px.
…details-header Co-Authored-By: adm <aditya.mathur@sentry.io>
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 10fb22c. Configure here.
Contributor
|
21 screenshot changes — 21 changed · 0 added · 0 removed Review screenshots in Frameshift
Show 12 more changed screenshots
3 more changed screenshots in Frameshift. |
The event details header wrapped its timestamp onto a second line next to the navigation controls. Show it to the second in the sans face on one line, and keep milliseconds in the tooltip. Group event detail fields in the same card that Conversation details use. Move that card into DetailsList as DetailsCard so both panels share it. Groups inside a card, such as tool input and output, use a divider. Co-Authored-By: Aditya Mathur <aditya.mathur@sentry.io>
MathurAditya724
approved these changes
Oct 30, 2026
This branch was successfully deployed
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
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.
Improves how event details and the subagent event log look in the dashboard.
Event details header
Aug 7, 2026, 11:54:09 UTC) instead of a raw ISO string. It shows whole seconds in the sans face and stays on one line beside the actions, so it no longer wraps. The tooltip shows milliseconds, and the ISO value stays in thedatetimeattribute. Raw JSON is unchanged.#3 · …). It matches the?event=link parameter and the row label.ui/button-groupnamed "Event navigation", so they read as one control apart from close.ui/button-groupandui/separatorcame fromshadcn add button-group, trimmed to the parts we use, with dashboard tokens and radius.Event details body
DetailsCard, moved intoDetailsList). Groups inside a card, such as tool input and output, use a divider instead of a nested card.Subagent drawer event log
Nested drawers
Drawernow uses the shadcn Base UI drawer (ui/drawer, added withshadcn add drawerand trimmed to the parts we use) instead ofui/sheet. When event details open from inside the subagent drawer, they stack in front of it, like the shadcn nested drawer example. The parent scales back, shows a thin edge, and hides its content. The overlay, focus trap, scroll lock, and Escape behavior stay the same.BottomSheetand the mobile nav still useui/sheet.useSheet'sonOpenChangereads onlydetails.cancel(), so Dialog and Drawer roots can both use it.Swipe-to-dismiss to the right now works on these drawers, because the Base UI drawer supports it. Mouse text selection inside the content still works.
via Aditya Mathur.
--
View Session in Sentry