Use of "force" option should not disable reporter

[marob]

Use of "force" option should not disable reporter

[markelog]

Did the jscs fix all the errors? Or there some errors left, but they are not outputted?

[marob]

Nothing has been fixed as I have not set the boolean "fix" to true.

[markelog]

I'm trying to clarify this bit -

If the "force" option is enabled (true), the reporter is disabled: no detail of jscs violations are written in the console/file.

[marob]

Launching with "force: false" outputs some jscs violations (count of violations + detail of violations) in the console.
If we launch again with "force: true", the console output still has jscs violation count, but without details.

The problem is, if you use some reporterOutput (say Checkstyle or Junit), the content of the file is:

• empty with "force: true"
• filled with jscs violations with "force: false"

So the build can either not fail, either output the jscs violations in a file. But it can't do both.

[markelog]

We probably not gonna fix this at this point