JSON formatter outputs invalid JSON object due to "\n" in source property

Tell us about your environment

• ESLint Version: v3.8.1
• Node Version: v5.10.1
• npm Version: 3.10.9

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration: eslint --no-eslintrc --rule 'comma-dangle:[error,always-multiline]' --format json

What did you do? Please include the actual source code causing the issue.

var foo = {
  bar: "baz",
  qux: "quux"
};

What did you expect to happen? The returned object t be a valid JSON object.

What actually happened? Please include the actual, raw output from ESLint. The source property of the JSON object contains literal \n characters which are not valid in a JSON property value. It must be double-escaped (\\n) to be valid. Invalid output:

[{"filePath":"D:\\workspace\\work\\test.js","messages":[{"ruleId":"comma-dangle","severity":2,"message":"Missing trailing comma.","line":3,"column":14,"nodeType":"Property","source":"  qux: \"quux\"","fix":{"range":[39,39],"text":","}}],"errorCount":1,"warningCount":0,"source":"var foo = {\n  bar: \"baz\",\n  qux: \"quux\"\n};\n"}]

[platinumazure]

I’m a little confused by this report. The JSON you are showing seems to be valid (you are showing unquoted JSON, so I would expect \n to be interpreted as a backslash-n rather than an actual newline.

@vitorbal also took a look and fed your JSON through a validator, and it says it’s valid.

How are you using the JSON? I’m wondering if whatever tool you are feeding the JSON incorrectly into a tool, or maybe the tool has a bug deserializing the JSON?

[nzakas]

Closing, as this doesn’t appear to be an issue with ESLint.