Closed mlarcher closed 9 years ago
Hey @mlarcher,
I don't develop on Windows, but it appears that you are passing a glob pattern (i.e. **/*.scss
) to scss-lint
via the command line and it is receiving those literal strings. This tells me you aren't using a shell to expand those patterns ahead of time.
In case you aren't familiar, any glob pattern is expanded by your shell (e.g. typically bash
/zsh
if you're on some *nix distribution; for Windows it's cmd.exe
). Since cmd.exe
does not support wildcard expansion, this explains why the literal string is being passed along.
scss-lint
doesn't expand these patterns for you because asterisks are valid characters in file names. Thus whatever is invoking scss-lint
needs to expand the pattern and pass the list of files to scss-lint
.
Hope that helps.
Thanks for the quick reply. The initial problem is that scss-lint needs to operate on a large collection of scss files, and the windows command line is limited to 8192 characters, which is quickly reached when listing a collection of file paths. Would it be possible to provide an alternative way for scss-lint to get to the actual files ? Surely there must be some options available, don't you think ?
As long as all you're trying to do is lint files in a directory, you can just pass the directory. scss-lint
will recursively scan for any files ending with .scss
and lint them.
scss-lint /path/to/project/dir
Great, thank you.
According to https://github.com/juanfran/gulp-scss-lint/issues/51#issuecomment-142983831 it seems there is an issue in the way command line are handled in scss-lint. Here is the command line input:
and the corresponding output:
The content of .scss-lint.yml is:
Could you please tell us if this is a bug in the package, a misuse of the CLI, or something wrong in the yaml file, so that we know what needs fixing ?