Use .prettierrc.json
instead of eslint
prettier
rule to configure format options
#654
+5
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During #648 I have some clash between Prettier and ESLint:
I'm using an editor with support for both tools, however they have a different behaviour when dealing with quotes:
eslint
was using single quotes due to the inline configuration ofeslint.config.js
eslint-doc-generator/eslint.config.js
Lines 28 to 33 in f733170
prettier
was using the double quotes, which is prettier default due to the empty config in.prettierrc.json
eslint-doc-generator/.prettierrc.json
Line 1 in f733170
To resolve this inconsistency, I added the
singleQuote
option to.prettierrc.json
and removed it fromeslint.config.js
.There should be no further issues since the ESLint plugin now reads options directly from Prettier's configuration:
https://github.com/prettier/eslint-plugin-prettier?tab=readme-ov-file#options