Add CLI

[Snugug]

Make Sass Lint run-able via a command line command. The CLI Branch is where work is being done on this feature.

• Do not fail on error

Feedback Requested

What options should be available from the command line?

[davidgilbertson]

+1

Could it maybe be added to the readme that there isn't a CLI yet? I'm guessing you're about to have thousands of eager devs trying to get it working before realising that there is no CLI.

Also, this whole sass-lint thing is awesome, congrats on the 1.0 release!

[Snugug]

Done
https://github.com/sasstools/sass-lint/blob/master/README.md#cli

[Snugug]

Track progress on the CLI Branch
https://github.com/sasstools/sass-lint/tree/cli

[davidgilbertson]

Nice.

My thoughts on command line options would be to more-or-less mirror scss-lint. Of those the two I can imagine using would be:

• --config so that I can define a config file other than the default.
• --exclude
• I'm tempted to say a --files option to override the glob in the config file, but can't think of a use case.

[Snugug]

So currently, this is how the CLI is shaping up:

• sass-lint will use whatever is in the config file
• sass-lint '<file or glob'> will override the file or glob from the config file
• --no-exit will prevent the CLI from failing if there's an error

The config currently calls exclude ignore; I can swap them if need be and add that as an option.

I'm going to wait on #47 to land before providing a CLI for custom config.

[Snugug]

Custom Config file landed in the CLI branch, so this'll be part of the CLI when released

[davidgilbertson]

Sounds perfect. Do you have a ballpark ETA on this? Weeks, months?

[Snugug]

Probably days. It's working, just needs final tweaks.

On Aug 30, 2015, at 6:49 PM, David Gilbertson notifications@github.com wrote:

Sounds perfect. Do you have a ballpark ETA on this? Weeks, months?

—
Reply to this email directly or view it on GitHub.