Support directories about grunt-csscomb HOT 9 CLOSED

@lhtdesignde this should fix the issue #42

from grunt-csscomb.

Fixed in v4.0.0.

from grunt-csscomb.

Yes, you can already do :)

Please write code as follows.

grunt.initConfig({
    csscomb: {
        dynamic_mappings: {
            expand: true,
            cwd: '/assets/css/',
            src: ['*.css'],
            dest: '/assets/css/'
        }
    }
});

Add description on Readme.md.

from grunt-csscomb.

@t32k, I think the question was not so much about the support as about syntax: now you need to write 4 lines and @oswaldoacauan proposes doing the same thing with 1 line of code.

from grunt-csscomb.

@tonyganch Oh, I see. That's what it means...
OK, I'll think it.

from grunt-csscomb.

First of all, @oswaldoacauan is right, there is a comb.processPath() method that can be used for both files and directories.
Also, I'm not sure if anyone uses this plugin and sets destination path different from source one.
I have looked at some examples how people use this grunt task — dest and src are always the same.
So maybe the idea of having one-line settings is good.

But at the same time I don't think that we should invent any new rules of setting paths.
I have taken a look at grunt-contrib-jshint.
There is an example:

grunt.initConfig({
  jshint: {
    all: ['Gruntfile.js', 'lib/**/*.js', 'test/**/*.js']
  }
});

Maybe we should support the same workflow, so user can add .csscomb.json file to project's root and then add a few lines to Gruntfile:

...
  csscomb: {
    all: ['src/styles']
  }
...

This will process all supported files in src/styles directory and rewrite them if any changes are needed.
And those who want destination path to differ from source can still use current files: {} way.

from grunt-csscomb.

Yep, i think the @tonyganch described workflow is nice.

👍 for less lines in Gruntfile.js

from grunt-csscomb.

👍

from grunt-csscomb.

+1 is this possible already?

from grunt-csscomb.