fix(conversations): improve truncation of non-UUID conversation IDs#115978
Merged
Conversation
The conversation detail heading and breadcrumb were hard-truncating conversation IDs to 8 characters via .slice(0, 8). This works fine for UUIDs (e.g. showing 'a1b2c3d4') but produces nonsensical results for structured IDs like 'slack:C0B595QDZLL:1779310456.221179' → 'slack:C0'. Changes: - Heading: use CSS text-overflow ellipsis with a Tooltip that shows the full ID on hover (showOnlyOnOverflow), keeping .slice(0, 8) only for UUID-shaped IDs - Breadcrumb: same isUUID check; non-UUID labels show the full ID with a Tooltip, relying on the Breadcrumbs component's existing maxWidth and ellipsis handling for visual truncation This matches the pattern already used in the conversations table.
github-actions
Bot
added
the
Scope: Frontend
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.59% |
dcramer
added
the
Trigger: getsentry tests
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
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 3f580fb. Configure here.
Address cursor bot feedback: Heading from @sentry/scraps/text already supports an ellipsis prop that handles overflow/text-overflow/nowrap. Remove the ConversationHeading styled component and use the native prop directly, keeping only min-width/flex-shrink via the style prop for flex-item sizing.
github-actions
Bot
removed
the
Trigger: getsentry tests
dcramer
added
the
Trigger: getsentry tests
obostjancic
approved these changes
May 21, 2026
JonasBa
pushed a commit
that referenced
this pull request
May 21, 2026
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
2 participants
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.
Summary
The conversation detail heading and breadcrumb were hard-truncating conversation IDs to 8 characters via
.slice(0, 8). This works for UUIDs (showinga1b2c3d4) but produces nonsensical results for structured IDs likeslack:C0B595QDZLL:1779310456.221179→slack:C0.Changes
Heading (
conversationSummary.tsx):text-overflow: ellipsiswith aTooltip(showOnlyOnOverflow) that reveals the full ID on hover.slice(0, 8)only for UUID-shaped IDsBreadcrumb (
layout.tsx):isUUIDcheck; non-UUID labels pass the full ID with a wrappingTooltipBreadcrumbscomponent's existingmaxWidth/ ellipsis handling for visual truncationThis matches the pattern already used in the conversations table for non-UUID IDs.
Evidence
Reported via this conversation where the ID
slack:C0B595QDZLL:1779310456.221179was rendered asslack:C0in both the heading and breadcrumb.Verification
tsc --noEmit) — no errors on changed filesnode_modules); existing tests should pass unchanged since the rendering logic only differs for non-UUID inputs