-
Notifications
You must be signed in to change notification settings - Fork 8
Migrated to postcss 8; add ability to use multiple namespaces #83
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
base: master
Are you sure you want to change the base?
Conversation
Thank you so much, this is great! Could you add some tests for the "multiple namespaces" case, I'm not 100% sure I understand the use-case here without examples :) |
Sure. An example of multiple namespace usage is here: In that particular example, I am providing multiple namespaces for a plugin style that integrates with Divi, as the selectors are different depending on whether a Divi theme is used, or only the Divi Builder. For example, with this configuration: require('postcss-selector-namespace')({namespace: '#et-main-area, #et-boc'}) This: .component {
/* ... */
} Becomes this: #et-main-area .component,
#et-boc .component {
/* ... */
} |
Since not everyone uses a custom line-height in the editor instead of inserting line breaks for clarity.
I realise that this pull request may not be the easiest to review as the code has been migrated to the postcss 8 api.
See: https://evilmartians.com/chronicles/postcss-8-plugin-migration
Also solves: #8