Introduce JSON schema for deny.toml #635
Draft
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.
Status: going through trailing design iterations, there is enough code to start thinking of making it into a separate tool living in a separate repo.
This is the work that is intended to close #632
This PR is not complete yet, it already works nicely, but I want to improve it more. Almost nothing to review. It's just a draft PR that I'll try to finish as soon as I have time.
TODO
The things to do in this PR:
deny.schema.yml
with the remaining shape ofdeny.toml
configsdefault
annotations and enum documentation (not supported in any version)toml_span
TODO after merge
Make a PR to the SchemaStore repo with the entry for
deny.toml
file association.