main
Last change
on this file was d565449, checked in by stefan toskovski <stefantoska84@…>, 4 weeks ago |
Update repo after prototype presentation
|
-
Property mode
set to
100644
|
File size:
2.5 KB
|
Line | |
---|
1 | [
|
---|
2 | {
|
---|
3 | "name": "checkstyle",
|
---|
4 | "description": "Outputs results to the [Checkstyle](https://checkstyle.sourceforge.io/) format."
|
---|
5 | },
|
---|
6 | {
|
---|
7 | "name": "compact",
|
---|
8 | "description": "Human-readable output format. Mimics the default output of JSHint."
|
---|
9 | },
|
---|
10 | {
|
---|
11 | "name": "html",
|
---|
12 | "description": "Outputs results to HTML. The `html` formatter is useful for visual presentation in the browser."
|
---|
13 | },
|
---|
14 | {
|
---|
15 | "name": "jslint-xml",
|
---|
16 | "description": "Outputs results to format compatible with the [JSLint Jenkins plugin](https://plugins.jenkins.io/jslint/)."
|
---|
17 | },
|
---|
18 | {
|
---|
19 | "name": "json-with-metadata",
|
---|
20 | "description": "Outputs JSON-serialized results. The `json-with-metadata` provides the same linting results as the [`json`](#json) formatter with additional metadata about the rules applied. The linting results are included in the `results` property and the rules metadata is included in the `metadata` property.\n\nAlternatively, you can use the [ESLint Node.js API](../../integrate/nodejs-api) to programmatically use ESLint."
|
---|
21 | },
|
---|
22 | {
|
---|
23 | "name": "json",
|
---|
24 | "description": "Outputs JSON-serialized results. The `json` formatter is useful when you want to programmatically work with the CLI's linting results.\n\nAlternatively, you can use the [ESLint Node.js API](../../integrate/nodejs-api) to programmatically use ESLint."
|
---|
25 | },
|
---|
26 | {
|
---|
27 | "name": "junit",
|
---|
28 | "description": "Outputs results to format compatible with the [JUnit Jenkins plugin](https://plugins.jenkins.io/junit/)."
|
---|
29 | },
|
---|
30 | {
|
---|
31 | "name": "stylish",
|
---|
32 | "description": "Human-readable output format. This is the default formatter."
|
---|
33 | },
|
---|
34 | {
|
---|
35 | "name": "tap",
|
---|
36 | "description": "Outputs results to the [Test Anything Protocol (TAP)](https://testanything.org/) specification format."
|
---|
37 | },
|
---|
38 | {
|
---|
39 | "name": "unix",
|
---|
40 | "description": "Outputs results to a format similar to many commands in UNIX-like systems. Parsable with tools such as [grep](https://www.gnu.org/software/grep/manual/grep.html), [sed](https://www.gnu.org/software/sed/manual/sed.html), and [awk](https://www.gnu.org/software/gawk/manual/gawk.html)."
|
---|
41 | },
|
---|
42 | {
|
---|
43 | "name": "visualstudio",
|
---|
44 | "description": "Outputs results to format compatible with the integrated terminal of the [Visual Studio](https://visualstudio.microsoft.com/) IDE. When using Visual Studio, you can click on the linting results in the integrated terminal to go to the issue in the source code."
|
---|
45 | }
|
---|
46 | ] |
---|
Note:
See
TracBrowser
for help on using the repository browser.