-
Notifications
You must be signed in to change notification settings - Fork 357
Wonder Blocks: Remove deprecated semanticColor.text and semanticColor.border token instances #2627
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
…er with sc.border equivalents
…olor.core` WB tokens instead of the now deprecated sc.text and sc.border tokens
Size Change: +21 B (0%) Total Size: 472 kB
ℹ️ View Unchanged
|
npm Snapshot: PublishedGood news!! We've packaged up the latest commit from this PR (ec8dcd2) and published it to npm. You Example: pnpm add @khanacademy/perseus@PR2627 If you are working in Khan Academy's frontend, you can run the below command. ./tools/bump_perseus_version.js -t PR2627 If you are working in Khan Academy's webapp, you can run the below command. ./dev/tools/bump_perseus_version.js -s n -t PR2627 |
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.
I pushed one commit to utils/extract-css.js
(a tool that Mark is building to extract aphrodite styles to CSS modules), just to keep things current. Can you double-check I mapped them correctly?
I don't see any other instances of the deprecated semanticColor
symbols now.
"#21242c": "--wb-semanticColor-core-foreground-neutral-strong", | ||
"#5f6167": "--wb-semanticColor-core-foreground-neutral-default", | ||
"#b8b9bb": "--wb-semanticColor-core-foreground-disabled-default", | ||
"#ffffff": "--wb-semanticColor-core-foreground-inverse-strong", |
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.
Makes sense!
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @khanacademy/perseus@65.3.4 ### Patch Changes - [#2627](#2627) [`4788af376`](4788af3) Thanks [@jandrade](https://github.com/jandrade)! - Updates styles to use `semanticColor.core` WB tokens instead of the now deprecated sc.text and sc.border tokens ## @khanacademy/perseus-editor@25.0.4 ### Patch Changes - [#2627](#2627) [`4788af376`](4788af3) Thanks [@jandrade](https://github.com/jandrade)! - Updates styles to use `semanticColor.core` WB tokens instead of the now deprecated sc.text and sc.border tokens - Updated dependencies \[[`4788af376`](4788af3)]: - @khanacademy/perseus@65.3.4 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Summary:
Updates styles to use
semanticColor.core
WB tokens instead of the nowdeprecated sc.text and sc.border tokens, which were previously used
for text and border colors.
This change is part of the ongoing effort to standardize our new
core
semanticcolor tokens across repositories, so that we can have a consistent approach
with Design specs.
Docs: https://khan.github.io/wonder-blocks/?path=/docs/foundations-using-color--docs#core
Issue: "none"
Test plan:
Verify that the following components render without any visual changes: