Allow user to use SassBeautify anywhere about sassbeautify HOT 7 CLOSED

Hey, thanks for the info. I did not know this feature existed! We can use sass-convert to beautify CSS (somewhat). It's not perfect though! For example, it does not beautify the css selectors very well.

EG, try beautify this css:

article        .title {
        color: red;
}

(The underlying command would be this: sass-convert --to scss --from scss style.css)

I don't think sass-convert was intended to beautify CSS, thus there's a very real chance this won't work sometime in the future, but there's no harm in releasing this as a 'hidden' feature. This should be an easy change, I will add it soon!

from sassbeautify.

Ok I've added this feature but as mentioned before I'm going to keep it 'hidden' and undocumented. Upgrade your packages to pull down this change. ( I can't say exactly when you'll be able to pull down this latest change, but likely by the time you read this it will be updated, otherwise, give it a couple of hours.) I'll close this ticket when I've verified this works when installing/upgrading the package via sublime package control.

from sassbeautify.

I'm going to close this ticket as the ST package control has updated this package. I had to uninstall and then re-install this package to get the latest changes (instead of just upgrading).

from sassbeautify.

Hi ! (sorry, late answer)
I just tested, and it works on .css files.
Not on an unsaved file (without .css or .scss extension), so we can't use it "anywhere" but nevermind !
Thank you for your work ! :)

from sassbeautify.

I don't think I'll be able to make it work on unsaved files as I need the file extension to determine what type of file the user is trying to beautify.

from sassbeautify.

Yeah, I looked at the code here 9595a99 and I saw you needed the file extension, that's why I didn't insist ! :)

from sassbeautify.

FYI, here's the cause of the upgrading issue now that I've moved to using tags: wbond/package_control_channel#2480

from sassbeautify.