Add schema-parity to tooling data (#2464) - #2475
Open
Prachidg wants to merge 1 commit into
Open
Conversation
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 #2475 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 31 31
Lines 695 695
Branches 215 215
=========================================
Hits 695 695 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Addition of a new tool to the JSON Schema Ecosystem registry.
Issue Number:
Screenshots/videos:
N/A (Data/registry update only)
If relevant, did you update the documentation?
N/A
Summary
This PR adds the
schema-paritylibrary todata/tooling-data.yaml.schema-parityis a differential testing harness that checks whether a generated JSON Schema accepts exactly the same set of values as the runtime validator it was generated from (e.g. Zod, ArkType, Valibot, TypeBox, etc.) and identifies any value ranges/cases where they disagree.Does this PR introduce a breaking change?
No
Checklist