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

Bless #26

Open
icylace opened this issue Oct 31, 2014 · 4 comments
Open

Bless #26

icylace opened this issue Oct 31, 2014 · 4 comments

Comments

@icylace
Copy link

icylace commented Oct 31, 2014

Would it be worth it to include direct support for Bless or is that too rare of a use case nowadays ?

@icylace icylace changed the title blesscss Bless Oct 31, 2014
@7studio
Copy link

7studio commented Oct 31, 2014

I think this case can arriving quickly with the pre/post-processors because of the ease to import stylesheets.
For example, rework has already a plugin to check this use case: https://github.com/reworkcss/rework-ie-limits
I don't know on which parser Bless is operating but IMHO if we want this kind of features, it would be interesting which uses PostCSS ;)

@iamvdo
Copy link
Owner

iamvdo commented Nov 18, 2014

Definitely a great improvement. I see 2 cases:

  • Only inform that there are more than 4095 selectors (as rework-ie-limits does). It's simpler and integrated well in Pleeease.
  • Split CSS and create many files (as Bless does). More complex and need to change how Pleeease handle files.

What's the best for you?

@icylace
Copy link
Author

icylace commented Nov 19, 2014

Ideally, both cases would be supported. Perhaps Pleeease should have a simple API so that a plugin for it could take on the added complexity? Not sure if that works philosophically because Pleeease is positioned as an "all-in-one" solution.

@Dobby89
Copy link

Dobby89 commented May 8, 2015

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants