lex148 / beautiful-css Goto Github PK

This is unusable, it doesn't work with sass or less, TROLOLOLOL.

I like the idea behind this tool and when I plopped in my code it saved my about 1000 lines of code. The only thing keeping me from implementing this is the fact that it sorts my code alphabetically without my consent.

I know my code's organization and I like to keep it that way. I don't mind combining properties but I'd like to keep most of it in relatively the same structure. If there was an option to turn the alphabetical sorting off I'd love that.

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can imagine, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.

The actual processing ought to be scoped so that anything nested under an @media query is isolated and the actual declarations are treated properly. Off the top of my head, the main things:

• Recognize @media queries and their declarations properly.
• Since source order of selectors gets mucked up, the easiest solution would be to extract queries and append to the end of the file while respecting their original order.
• At that point, might as well merge exact queries prior to processing.

If it's alright, I'll take a better look at things later when I've got a bit more free time. Really interested in seeing how this gem can play out.