add eslint-plugin-json and lint workflow #5101
Merged
Conversation
This file contains 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
turbocrime
force-pushed
the
turbocrime/formatter-ci
branch
from
ed1c096 to
1f9df10
Compare
turbocrime
force-pushed
the
turbocrime/formatter-ci
branch
from
1f9df10 to
3fcd574
Compare
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.
adding a linter could prevent malformed json from accidentally entering the registry.
the workflow is based on your existing workflows.
the repository currently passes this lint workflow.
this 'recommended' eslint config from eslint-plugin-json would have caught #5088
as an example, that failure is duplicated in #5102