-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Gutenberg Plugin: Format all JSON files using Prettier formatter #30714
Conversation
e6ea5f8
to
d73ff1a
Compare
Size Change: +857 B (0%) Total Size: 1.43 MB
ℹ️ View Unchanged
|
😲 |
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.
Quite a few files to review 😆
It looks like most of the fixes are changes to the test fixtures and range parameters,, so those passing will be a good confirmation. Will the auto generated fixtures need to be updated?
I updated the manifest tool to include a new line when it generates, this clears up that error.
Good observation. It's hard to tell, but as long as we don't run checks on the formatting it's acceptable. I wanted to split efforts into smaller steps as much as possible. |
Description
Related to #30240 where @ockham proposed we start formatting more types of files, other than JS files.
It's a result of executing:
npx prettier --format **/*.json
Let's see how it plays out in practice with CI checks.
Known issue
See https://github.com/WordPress/gutenberg/pull/30714/checks?check_run_id=2321165368#step:9:6
docs/manifest.json
file gets a different end of file when generated withnpm run docs:build