-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add lint check into CI #11
Conversation
@@ -17,7 +17,8 @@ | |||
"css": "node ./scripts/css.js", | |||
"dev": "node ./scripts/dev.server.js", | |||
"watchTest": "karma start ./config/karma.config.js", | |||
"lint": "prettier --write src/**/* tests/**/*", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tu devrais changer le script qui est rouler dans le pre-commit hook aussi plus bas ligne 27
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oups je l'ai pas vu en effet. C'est updated 👌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ouin tu peux ignorer les trucs auto-generated comme package-lock.json ? Sinon j'ai l'impression que sa vas spammer a chaque fois :P
L'issue avec ca @mikegron c'est que imaginons User A fais un npm install depuis un linux, ca va le générer en LF. User B fais un npm install depuis un windows, ca va le générer en CRLF, ce qui génère du changement. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
To ensure an opinionated code formatting, running prettier --check on the CI will prevent any commit to get validated by the CI if the code does not respect the prettier configuration.