-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Pre-commit Hooks & Improving Prettier/ESLint rules #439
Conversation
Quality Gate passedIssues Measures |
@kriszyp Updated PR 🙂 |
"quoteProps": "consistent", | ||
"singleQuote": true, | ||
"trailingComma": "es5", | ||
"useTabs": true, |
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.
I presume you are going to have a lot of whitespace updates in your commits going forward with this. Do you want that?
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.
Hmmm 🤔 I'll look into:
- Creating a separate PR running prettier & ESLint on the entire app
and/or - Investigating if it's possible to run prettier and not affect the git history
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.
Usually the strategy is to add (mass) prettier/lint commits in .git-blame-ignore-revs: https://github.com/HarperDB/harperdb/blob/main/.git-blame-ignore-revs
I just didn't know if you really wanted to do that right now.
Overview
"prettier --write --ignore-unknown"
&"eslint --fix"
run as pre-commit hooks