-
Notifications
You must be signed in to change notification settings - Fork 115
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
Use @primer/primitive
v8 color CSS vars with fallbacks
#2083
Conversation
🦋 Changeset detectedLatest commit: 7d467d6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
@primer/primitive
v8 color CSS vars with fallbacks
missing_vars = matches.map { |match| match[0] } | ||
assert_equal 0, matches.length, "CSS variables are missing fallbacks: #{missing_vars.join(', ')}" | ||
end | ||
end |
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.
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 added some logic in to point at the line and column so it's easier to find the failure.
Authors: Please fill out this form carefully and completely.
Reviewers: By approving this Pull Request you are approving the code change, as well as its deployment and mitigation plans.
Please read this description carefully. If you feel there is anything unclear or missing, please ask for updates.
What are you trying to accomplish?
Using Stylelint, this PR replaces all color CSS vars with the new version from Primitives that we're testing behind a feature flag in github/github. PostCSS automatically adds fallback values at build time, and stylelint will ensure we only use new color tokens going forward with linting.
Screenshots
Integration
No, the feature flag is already in place.
List the issues that this change affects.
https://github.com/github/primer/issues/1410
Risk Assessment
What approach did you choose and why?
npm run lint:stylelint:fix
and some manual find/replaceAnything you want to highlight for special attention from reviewers?
Please check that the build CSS files all have fallback values (see the build in the checks section)
Accessibility
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.