Build: Use JSONLint to format JSON files #2591
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nschonni
commented
Jul 2, 2025
| } | ||
| ,{ | ||
| "@context": { | ||
| "@version": 2.0, |
There was a problem hiding this comment.
Seems like a bug, and should probably be quoted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this pull request(PR) do?
Separate from the larger PR that enables Lintspaces on all the files, I was looking for a way to repeat the formatting consistently.
This adds a separate task to run the formatting, but I noticed the regular
jsonlint:allpass doesn't actually check the format (outside of broken JSON), so relied on Lintspaces for now.An alternate way to check this in CI, would be to run the format and then fail if there is any
git diffContribution category (please only choose one)
General checklist
Related issues