chore: format JSON files in Trunk #19541
Merged
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.
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[X] Other, please explain:
Update the build
What changes did you make? (Give an overview)
I noticed that after #19354 running
node bin/eslint
was reporting errors for.json
files that were not caught by Trunk in CI, so I updated the Trunk config to lint and auto-format JSON files as well. I also updated the Prettier config to apply the same formatting rules for.json
files also to.jsonc
and.json5
files and to the.c8rc
file, and I updated the ESLint config so that.jsonc
files with trailing commas can be parsed. Then I fixed the lint problem indocs/package.json
and let Prettier do the rest.Is there anything you'd like reviewers to focus on?