-
Notifications
You must be signed in to change notification settings - Fork 146
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
refactor: rebrand SpotlightPopoverTour
#1952
refactor: rebrand SpotlightPopoverTour
#1952
Conversation
snitin315
commented
Jan 11, 2024
•
edited
Loading
edited
- No breaking changes.
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit db76400:
|
✅ PR title follows Conventional Commits specification. |
df3d814
to
125968e
Compare
@@ -110,12 +110,12 @@ export const BasicExample = ` | |||
> | |||
<Box width="100%" display="flex" gap="spacing.4"> | |||
<SpotlightPopoverTourStep name="step-1"> | |||
<Box padding="spacing.4" backgroundColor="brand.gray.400.lowContrast"> | |||
<Box padding="spacing.4" backgroundColor="interactive.border.gray.faded"> |
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.
why are we using interactive color on a box? should be surface right?
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.
Hmm, this value is mapped in the codemod. I think we should update this with surface.border.gray.muted
.
"brand.gray.400.lowContrast": "interactive.border.gray.faded", |
interactive.border.gray.faded
& surface.border.gray.muted
have the same value.
muted: globalColors.neutral.blueGrayLight.a100, |
faded: globalColors.neutral.blueGrayLight.a100, |
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.
@snitin315 put this on a TODO somewhere, we will take this up as a separate PR.
Let's merge this component. This is just an example file.
// cc @kamleshchandnani
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.
why separate PR? one line change hai lets do it?
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.
Are we sure about this token? We are setting border color in backgroundColor
.
And I'm not sure we should also map this to border on the colorMapping.json file - since we don't know if it's being used as border/background or surface.
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.
This was previously discussed in #1883 (comment)
So currently, we migrate every token to surface tokens by default via the colorMapping.json
, then we try to update these tokens contextually based on usage wherever possible.
// Update color token value based on the context |
blade/packages/blade/codemods/brand-refresh/transformers/__tests__/migrate-colors.test.ts
Line 38 in 40dd304
it('should update token values contextually', async () => { |
However, the issue with brand.gray.*
tokens is that not all the tokens have their equivalent in surface tokens. hence we have them mapped to border.*
. So we need designers inputs here.