Implement different reporters about gulp-jscs

[sindresorhus]

linting and reporting should be separated: $.jscs() and $.jscs.reporter('my-reporter') (similarly to https://github.com/spenceralger/gulp-jshint)

👍

we cannot use node-jscs reporters directly - they all write output to console.log, so they need to be ported and modified

Can you open a ticket on jscs about changing that? Manually porting all future reporters isn't feasible.

What are your thoughts?

Sure, I don't see the use-case myself, but I know some rely on it.

[sindresorhus]

Note to self: Also need a fail reporter like gulp-jshint.

[johnpapa]

+1 ... would like to see the reporter option as a pass through

[wylieconlon]

@sindresorhus The use case I see is to fail a build (on TeamCity, for example) if code doesn't pass style checks. Integration with https://github.com/wurmr/jscs-teamcity-reporter is an example

[sindresorhus]

I won't have time to implement this for a good while, but PR welcome :)

[wurmr]

If it helps anyone looking to implement this, grunt-jscs does a similar thing and allows for custom output routing and custom reporters.

Personally right now I'm using gulp-grunt to wrap that to do my jscs checking in TeamCity.

[sindresorhus]

#57 implemented the first stage for reporter supporting, an jscs object attached to the file object with some reporter data.

Next step is implementing:

• reporter fetching (depends on jscs-dev/node-jscs#867) (implemented #41 (comment) in jscs 1.10.0)
• built-in fail reporter

[UltCombo]

@sindresorhus what's left for you to tick that first checkbox?

Guess I'll give this a stab tonight.

[UltCombo]

#66

[jamesmorgan]

+1 this would be nice

[idefy]

Until this is available, you should look at this plugin that allows to use jshint reporters:
https://github.com/gonsfx/gulp-jscs-stylish