-
Notifications
You must be signed in to change notification settings - Fork 195
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
feat(tokens): add spectrum and express to tokens package #2742
Conversation
🦋 Changeset detectedLatest commit: 170fb3e The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
🚀 Deployed on https://pr-2742--spectrum-css.netlify.app |
File metricsSummaryTotal size: 4.64 MB* Table reports on changes to a package's main file. Other changes can be found in the collapsed Details section below.
Detailstokens
* Results are not gzipped or minified. * An ASCII character in UTF-8 is 8 bits or 1 byte. |
697435f
to
c82818b
Compare
08529db
to
754d5b0
Compare
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.
Let's get that pre-release rollin'
96c2ce5
to
4078e32
Compare
4078e32
to
92f5e39
Compare
45cebeb
to
c916451
Compare
c916451
to
170fb3e
Compare
SWC branch: adobe/spectrum-web-components#4442 |
Description
In preparation for our migration to a Spectrum 2-focused project, this PR adds component-specific theme assets to our token package. In this way, we are connecting the system overrides with a particular version of the token system (namely S1). When S1 content is removed, this will include removing the system theming approach entirely. By loading the theme and bridge assets for your component, you will be able to support S1 and S2 in parallel if you so wish (note that for this to work, you will still have to load both the S1 and S2 releases of the @spectrum-css/tokens package in tandem and with appropriate scoping).
In this PR we are adding 3 addition steps to our build process for only those components that support system theming:
<component-name>/themes/spectrum.css
output totokens/components/spectrum/<component-name>.css
<component-name>/themes/express.css
output totokens/components/express/<component-name>.css
<component-name>/index.css
with areferencesOnly = true
flag for the Splintinator postcss plugin to output a new asset:tokens/components/bridge/<component-name>.css
which will contain the mapping of component-specific custom properties to their--system
prefixed pairing. This allows S2 base CSS to continue to work with S1 tokens (until a time that a new breaking change is released for that component).How and where has this been tested?
Please tag yourself on the tests you've marked complete to confirm the tests have been run by someone other than the author.
Validation steps
Regression testing
Validate:
Screenshots
To-do list