[TECH] Formater le code avec Prettier. #104
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
octo-topi
added
cross-team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🦄 Problème
Voir 1024pix/pix#3538
🤖 Solution
1024pix/pix#3538
Lors de l'application de
lint:fix, je passe de 423 erreurs à 183 🤔 de typecomma-dangle(règle mise à jour dans la version de eslint)J'ai pourtant appliqué les mêmes changements que sur API, il n'y a que la version de eslint qui diffère.
Est-ce dû à
eslint-plugin-prettier? Il y a une issue🌈 Remarques
Cette PR est dédicacée au linterman @sbedeau ; on continue ton travail !
Montée de version de
eslint(breaking changes)💯 Pour tester
Vérifier que la CI passe.
Introduire une erreur, vérifier que
npm run lintrenvoie <> 0