Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

added directory support for cli #275

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

I added directory support for cli because we use a lot of file in the same subdirectory (eg: src/ and want to make a single file like application.css and application.min.css) and we felt us naked without this =) If I added this then I think send a pull request.

If the given "file" is a directory
then :syntax option will be skipped and guessing from file extension.

Example: sass src/ assets/application.css

I know not a perfect and nice additional but works. If i will have time (and someone else don't make it) I make a better solution. If this solution is not ok then please tell me what is the problem.

Thanks: Balazs Nadasdi

@Yitsushi Yitsushi directory support.
If the given "file" is a directory
  then :syntax option will be skipped and guessing from file extension.

Example: sass src/ assets/application.css
7133315
Contributor

nex3 commented Feb 13, 2012

How is this different than sass --update src:assets?

this command creates separated files
$ sass --update src:assets
$ ls assets
one.css three.css two.css

and this patch make just one file (or one output stream to stdout)
$ sass src assets/app.css
$ ls assets
app.css

Nothing more =) So i don't need to merge these files with an other app or i don't need to make a main.sass what contains only @imports's

Contributor

nex3 commented Feb 13, 2012

Use partials.

@nex3 nex3 closed this Feb 13, 2012

Oh yeah before i modified this our base.sass was 63 lines thats only @import's

@import 'page'
@import 'main'
@import 'editor'
@import 'enterpage'
@import 'galleries'
@import 'images'
@import 'members'
@import 'messages'

And i we created a new file we need to add this it to somewhere. =/ So partial is NOT a nice solution for it. =) because a little annoying.

Contributor

nex3 commented Feb 15, 2012

Handling many imports has been discussed to death elsewhere. The upshot is that we don't support it because it makes the ordering of the imports unclear, but if you really want it you can define a custom importer.

Thx =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment