Add rsonschema to JSON Schema ecosystem#2390
Add rsonschema to JSON Schema ecosystem#2390dariocurr wants to merge 1 commit intojson-schema-org:mainfrom
Conversation
Closes json-schema-org#2383 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Hi @dariocurr! Thanks a lot for your contribution! I noticed that the following required information is missing or incomplete: kind of change description Please update the PR description to include this information. You can find placeholders in the PR template for these items. Thanks a lot! |
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2390 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 30 30
Lines 672 672
Branches 211 211
=========================================
Hits 672 672 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Adds rsonschema to the website’s JSON Schema tooling ecosystem list as a validator implementation.
Changes:
- Added a new tooling entry for
rsonschema(Rust/Python validator) with metadata (source, homepage, license, dialect support, compliance, lastUpdated).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| compliance: | ||
| config: | ||
| docs: 'https://github.com/hiop-oss/rsonschema' | ||
| instructions: 'tested against the JSON-Schema-Test-Suite' |
There was a problem hiding this comment.
The compliance.config.instructions field is intended to describe actionable steps/configuration needed to make the tool maximally compliant, but here it’s being used as a general statement (“tested against the JSON-Schema-Test-Suite”). This will read oddly in the UI (it’s rendered under an “Instructions” heading) and doesn’t match the schema’s description for this field. Consider either (a) moving this statement to toolingListingNotes and removing compliance, or (b) changing instructions to concrete steps (and updating docs to point to the specific page/section that explains those steps).
| compliance: | |
| config: | |
| docs: 'https://github.com/hiop-oss/rsonschema' | |
| instructions: 'tested against the JSON-Schema-Test-Suite' | |
| toolingListingNotes: 'Tested against the JSON-Schema-Test-Suite.' |
What kind of change does this PR introduce?
Feature — adds a new tool to the JSON Schema ecosystem listing.
Issue Number:
Screenshots/videos:
N/A
If relevant, did you update the documentation?
N/A — this is a data-only change to
data/tooling-data.yaml.Summary
Adds rsonschema to the JSON Schema tooling ecosystem as a validator for Rust and Python. It is a high-performance JSON Schema validator designed for low-overhead and memory-efficient validation, supporting draft 2020-12 and tested against the JSON-Schema-Test-Suite.
Does this PR introduce a breaking change?
No.
Checklist