feat: Add Blaze4J tool to tooling data #1838
Open
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 kind of change does this PR introduce?
This PR adds the Blaze4J tool to the tooling-data.yaml file. Blaze4J is a high-performance Java wrapper for the Blaze JSON Schema validator, built as part of GSoC '25.
Issue Number:
If relevant, did you update the documentation?
Summary
This PR adds the Blaze4J tool to the
tooling-data.yaml
file. Blaze4J is a high-performance Java wrapper for the Blaze JSON Schema validator, built as part of Google Summer of Code 2025 (GSoC '25).Key Highlights
Does this PR introduce a breaking change?
No - This is an additive change to the tooling database
Checklist
Please ensure the following tasks are completed before submitting this pull request.