Skip to content
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

The best approach for pseudo-elements? #184

Closed
CDNRocket opened this issue Oct 14, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@CDNRocket
Copy link

commented Oct 14, 2018

What is the best approach for work with pseudo-elements like :before, :after, etc?
We need to create custom utilities/components?

Maybe should be a good idea to have a feature for this like: text-red:before?

@tlgreg

This comment has been minimized.

Copy link

commented Oct 14, 2018

Anything (almost?) could be applied to a pseudo-element. I don't think default config should include it though.

I could imagine it being a variant for the modules, which could be made with a plugin too if not in the core.

@hacknug

This comment has been minimized.

Copy link

commented Oct 18, 2018

You could probably use a plugin to register a new variant to do that. This was introduced in v0.6.2 and it's probably the easiest way to deal with your issue since you'll be able to carry that plugin between projects and also publish it as an npm package.

@CDNRocket CDNRocket closed this Oct 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.