Skip to content

Commit

Permalink
eslint: cleanup doc
Browse files Browse the repository at this point in the history
  • Loading branch information
simschla committed Jan 10, 2023
1 parent 6577e29 commit 0227e89
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 8 deletions.
8 changes: 4 additions & 4 deletions plugin-gradle/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -624,8 +624,8 @@ For details, see the [npm detection](#npm-detection) and [`.npmrc` detection](#n
The auto-discovery of config files (up the file tree) will not work when using ESLint within spotless,
hence you are required to provide resolvable file paths for config files, or alternatively provide the configuration inline.
The configuration is very similar to the [ESLint (Javascript)](#eslint-javascript) configuration. It differs in supported
styleguides and the requirement for a tsconfigFile.
The configuration is very similar to the [ESLint (Javascript)](#eslint-javascript) configuration. In typescript, a
reference to a `tsconfig.json` is required.
```gradle
spotless {
Expand Down Expand Up @@ -689,8 +689,8 @@ spotless {
The auto-discovery of config files (up the file tree) will not work when using ESLint within spotless,
hence you are required to provide resolvable file paths for config files, or alternatively provide the configuration inline.
The configuration is very similar to the [ESLint (Typescript)](#eslint-typescript) configuration. It differs in supported
styleguides and no requirement for a tsconfig (of course).
The configuration is very similar to the [ESLint (Typescript)](#eslint-typescript) configuration. In javascript, *no*
`tsconfig.json` is supported.
```gradle
Expand Down
8 changes: 4 additions & 4 deletions plugin-maven/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -724,8 +724,8 @@ For details, see the [npm detection](#npm-detection) and [`.npmrc` detection](#n
The auto-discovery of config files (up the file tree) will not work when using ESLint within spotless,
hence you are required to provide resolvable file paths for config files, or alternatively provide the configuration inline.

The configuration is very similar to the [ESLint (Javascript)](#eslint-javascript) configuration. It differs in supported
styleguides and the requirement for a tsconfigFile.
The configuration is very similar to the [ESLint (Javascript)](#eslint-javascript) configuration. In typescript, a
reference to a `tsconfig.json` is required.

```xml
<eslint>
Expand Down Expand Up @@ -803,8 +803,8 @@ For details, see the [npm detection](#npm-detection) and [`.npmrc` detection](#n
The auto-discovery of config files (up the file tree) will not work when using ESLint within spotless,
hence you are required to provide resolvable file paths for config files, or alternatively provide the configuration inline.

The configuration is very similar to the [ESLint (Typescript)](#eslint-typescript) configuration. It differs in supported
styleguides and no requirement for a tsconfig (of course).
The configuration is very similar to the [ESLint (Typescript)](#eslint-typescript) configuration. In javascript, *no*
`tsconfig.json` is supported.

```xml
<eslint>
Expand Down

0 comments on commit 0227e89

Please sign in to comment.