-
Notifications
You must be signed in to change notification settings - Fork 421
RI-7431: Change add key button view #4960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ArtemHoruzhenko
commented
Sep 16, 2025
| Before | After |
|---|---|
![]() |
![]() |
| } from 'uiSrc/telemetry' | ||
| import { | ||
| PrimaryButton, | ||
| Button, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: We also have an alias for a SecondaryButton that you can use :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed but I didn't like it. In general we added custom props to change the behavior and it became not clear which exactly variant we use.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually, the goal of having semantics in the way we build up our design systems is to hide the "implementation details" and make the end result look consistent everywhere.
Yes, we can always use the base components and customize them however we want, but I believe this is what we wanted to avoid when @pd-redis's introduced these semantic aliases. Anyway, we can talk about this in the future, it's not something critical/important right now :)
The base branch was changed.
Code Coverage - Frontend unit tests
Test suite run success5128 tests passing in 676 suites. Report generated by 🧪jest coverage report action from 3f61958 |

