-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Format JavaScript, CSS, and Markdown with Prettier #2670
Format JavaScript, CSS, and Markdown with Prettier #2670
Conversation
aed9a41
to
4b5d7c6
Compare
4b5d7c6
to
3935bad
Compare
Sorry for the messy force-pushing; I wanted to keep the commits single-purpose but I forgot to add a newline to |
Thanks |
@hyperupcall |
@GerryFerdinandus sure thing - i'll send a PR tomorrow |
* chore: Add config to format JS, CSS, and Markdown with Prettier * chore: Format files with Prettier * chore: Add Prettier format commit to `.git-blame-ignore-revs`
In the same style as #2255, this adds JavaScript, CSS, and Markdown to be formatted with Prettier (to the
.pre-commit-config.yaml
file). I would have added TOML to the mix, but the prettier plugin is in an alpha state.The
.prettierrc.json
file is based off theGruntfile.cjs
file; I wanted to minimize the impact of the change. In doing this, this solves problems I've had with editing the CONTRIBUTING.md or Gruntfile; saving the file no longer formats the file, which would have messed up the diff.The first commit adds the config; the second runs Prettier, and the third edits the
.git-blame-ignore-revs
file