-
Notifications
You must be signed in to change notification settings - Fork 235
chore(theme): include custom var css files in theme imports #3363
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
Westbrook
left a comment
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.
Great start. Don't forget to do the same for the Express files.
a49b957 to
5f26022
Compare
Tachometer resultsChromeaction-bar permalink
action-menu permalink
menu permalink
overlay permalink
picker permalink
popover permalink
slider permalink
split-button permalink
tooltip permalink
Firefoxaction-bar permalink
action-menu permalink
menu permalink
overlay permalink
picker permalink
popover permalink
slider permalink
split-button permalink
tooltip permalink
|
|
vrts are failing as expected on Dragged dropzone story, as those vars weren't getting into the component before now. |
|
Looks good here! Cycle the VRT hash and this should be good to go. |
b10c30a to
e9e9419
Compare
25bc303 to
31192df
Compare
Westbrook
left a comment
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.
LGTM!
Description
Some of the files within the Spectrum CSS core tokens packages weren't being imported to be used in the
themetools, even though we are importing them in thestylestools. Added imports for these files so that we can consume these custom variables, as well.Related issue(s)
Motivation and context
Missing import
How has this been tested?
Screenshots (if appropriate)
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main.