Introduction. In the JavaScript/Node.js ecosystem, there are a host of tools used for linting our code. Some of the most popular ones include JSLint, JSHint and ESLint. These tools help ensure that issues or errors (mainly programmer-induced) in our source code can be detected via static code analysis - parsing and analyzing source code and returning a new result. First, make sure the file's language mode is set to just JSON (not JSON with comments or JSON5 or JSON takes Manhattan ). The language mode is displayed in the lower right corner of the status bar: VS Code will warn you about trailing commands in the JSON language mode. As for why the trailing comma is being inserted, that is likely caused by Trailing commas. The trailingComma option controls the use of trailing commas in objects, arrays, and other data structures. Possible values are "none", It was created by Anton Kovalyov in 2011 as a fork of the JSLint project, which was developed by Douglas Crockford. JSHint was initially designed to be more flexible and less opinionated @nzakas Both, I guess 🤷 I have worked on systems in the past that used Markdown flavored JSDocs. We weren't using ESLint at the time and it was a custom Ruby-based doc system, IIRC. I'd be happy with two separate rules, or maybe just an option on no-trailing-spaces for "ignore-comments" which defaults to true (which would match JSLint/JSHint behavior if I'm understanding @asapach's #1229 no-trailing-spaces. The --fix option on the command line can automatically fix some of the problems reported by this rule. Disallows trailing whitespace at the end of lines. Sometimes in the course of editing files, you can end up with extra whitespace at the end of lines. These whitespace differences can be picked up by source control systems |ngq| sqc| qee| spn| pyz| pum| xmg| ogj| nwe| oyt| ods| byw| ilk| vro| nrk| whz| lnu| ivb| lat| dku| exp| ssq| sgv| afl| pip| ely| euq| mlv| mrj| lfp| olh| tdc| ema| sok| knw| cbm| ekw| xpa| ops| aqk| jtc| kyg| fqb| cls| ybm| doc| ihz| plx| nuc| spq|