-
Notifications
You must be signed in to change notification settings - Fork 186
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
Wrap styles of BpkLink and bpk-stylesheets in layers #3102
Conversation
packages/bpk-stylesheets/index.scss
Outdated
@include bpk-focus-indicator; | ||
} | ||
@layer utility { | ||
/* stylelint-disable-next-line no-duplicate-at-import-rules, no-invalid-position-at-import-rule */ |
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.
Had to disable two lint rules here, mixins needs imported twice, each for the two layers.
This could be solved by combining theme and utility into one layer
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 was going to say everything in this file should come under one layer that I would see as base
as this is core across everything and acts as the base the system then builds on
Visit https://backpack.github.io/storybook-prs/3102 to see this build running in a browser. |
Visit https://backpack.github.io/storybook-prs/3102 to see this build running in a browser. |
@@ -16,65 +16,67 @@ | |||
* limitations under the License. | |||
*/ | |||
|
|||
@import '~normalize.css'; | |||
@import '../bpk-mixins/index.scss'; | |||
@layer base { |
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 suggest that before this line we define all the layers upfront, something like:
@layer base, components, overrides;
Superseeded by #3111 |
A test of using @layer in css to fix upstream a CSS specificity bug in footer
Remember to include the following changes:
README.md
(If you have created a new component)README.md