Skip to content

Conversation

@JonasBa
Copy link
Member

@JonasBa JonasBa commented May 20, 2025

Changes replay timeline nodes to use graphic tokens.

Note that the colors are slightly more vibrant in the new theme, particularly the yellow and danger tokens seem to stand out more. The current change modifies the look for both themes, but I'd be happy to gate this to UI2 only if that's what you'd prefer.

Before
CleanShot 2025-05-20 at 11 22 21@2x
After
CleanShot 2025-05-20 at 11 22 26@2x

UI2 Before
CleanShot 2025-05-20 at 11 24 03@2x

UI2 After
CleanShot 2025-05-20 at 11 23 52@2x

Fixed DE-6

@JonasBa JonasBa requested a review from a team as a code owner May 20, 2025 15:29
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 20, 2025
}),
'ui.blur': () => ({
color: 'purple400',
color: 'accent',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we not keep using the actual color values, or maybe like make new token names? I'm thinking like, a blur is not an accent, it doesn't map like that imo

cc @Jesse-Box

Copy link
Member Author

@JonasBa JonasBa May 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we not keep using the actual color values, or maybe like make new token names? I'm thinking like, a blur is not an accent, it doesn't map like that imo

cc @Jesse-Box

We are ironing out the tokens, that will be the path forward, but we are not quite there yet.

Ultimately, we do want to guide folks away from using colors directly, and that Color type is one thing I'd like to see less of in the codebase. Main reason is that using that type gives you access to all theme colors, and so if we accept it in some generic component, like for example our Icons, we end up with a rainbow of colors for icons in production, as there is no way to enforce that e.g. only one type of gray color is used.

I agree, about the name maping, I'll defer to Jesse for that. Ultimately, what we want to encourage is for people to define their own variants, something that makes semantic meaning for the variants that they are encapsulating over, as it will be hard for us to do that, but also, we won't be able to find mapping that intuitively work for everyone.

An alternative approach here that I would recommend is creating a custom <IconNode variant='error | interaction | ...'/> that maps to a concept in replay, and then inside the IconNode, toggle the colors based off that variant. This way, we would avoid passing color aliases or value around, but also have an enumerated variant set that we could toggle on in different places as well

@ryan953
Copy link
Member

ryan953 commented May 20, 2025

colors seem fine in the before/after for ui1 and ui2 👍

@JonasBa JonasBa merged commit 6f8ac74 into master May 21, 2025
43 checks passed
@JonasBa JonasBa deleted the jb/replay/breadcrumbs-chon-DE-6 branch May 21, 2025 13:23
andrewshie-sentry pushed a commit that referenced this pull request Jun 2, 2025
Changes replay timeline nodes to use graphic tokens. 

Note that the colors are slightly more vibrant in the new theme,
particularly the yellow and danger tokens seem to stand out more. The
current change modifies the look for both themes, but I'd be happy to
gate this to UI2 only if that's what you'd prefer.

Before
![CleanShot 2025-05-20 at 11 22
21@2x](https://github.com/user-attachments/assets/305fa274-1649-4a76-b675-f2c9a63cfa93)
After
![CleanShot 2025-05-20 at 11 22
26@2x](https://github.com/user-attachments/assets/107d3630-4d85-4c02-be97-55f9b7a25157)

UI2 Before
![CleanShot 2025-05-20 at 11 24
03@2x](https://github.com/user-attachments/assets/e02f658a-ba29-40b3-a347-4a958073c6ad)

UI2 After
![CleanShot 2025-05-20 at 11 23
52@2x](https://github.com/user-attachments/assets/2a7eae69-9174-427a-96ab-88938e37aa8d)

Fixed DE-6
@github-actions github-actions bot locked and limited conversation to collaborators Jun 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants