-
Notifications
You must be signed in to change notification settings - Fork 226
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
Support dynamic generation of classes #161
Comments
I wouldn't be against the idea, but it does quickly move SUIT out of the 'future facing CSS' realm. Would be nice to be able to configure this to use 12, 16, 24 etc though. |
Maybe theres an alternative -
Something to think about at least. |
I see, so each package would contain the output of the postcss tools? Could work. Might also give more weight to moving the packages into a single repo to facilitate this. |
I can understand the need for that, but I have reservations against this and would like SUIT CSS to stay true to the "future facing CSS' realm." I think this should stay at user level. |
Maybe a broader question as it could apply to several repos, but what do people think of using postcss plugins like postcss-for to make the generation of some of these classes dynamic?
I have done this in my own projects, and think it would likely be too much of a can of worms to include here, but thought I'd start the discussion.
The text was updated successfully, but these errors were encountered: