CLI option --color is missing in documentation

The command line option --color is actually useful to enforce ANSI color codes when outputting to a pipe, e.g. in a Grunt task.

Apparently, this options is supported in ESLint 2.8.0, but it’s missing in the online doc and also in the output of

eslint -h

[nzakas]

@ralfstx @meeber as I mentioned above, our tool for handling CLI output, optionator, does not support outputting both options. We use this both on the command line and to generate the documentation, so this isnt a matter of just updated the docs.

If anyone has a suggestion for how to overcome that limitation, we are open to suggestions.

Also, keep in mind that we have almost 200 open issues. We can’t fix every issue that is filed, so we need to prioritize and close issues that we don’t intend to address. That may be frustrating, and that’s unfortunate. I just ask you to keep in mind that the ESLint team is entirely a volunteer team working in their free time on ESLint, and we are doing the best we can.

[ralfstx]

@platinumazure

the tone in this sentence …

Sorry for that, I didn’t mean to offend anyone. However, it’s frustrating when you take the time to report a minor issue and see it being closed without the issue being addressed.

Can you please provide exact repro steps showing where the absence of --color results in no colors …

Given a file with linting errors, the following command’s output contains colors:

eslint fileWithErrors.js

while the following command does not:

eslint fileWithErrors.js | cat

It’s all expected behavior, I’m just asking to add --colors to the documentation. If you point me to the source file, I’m happy to provide a pull request.