feat: Compiled JSON Schema type#98
Merged
Merged
Conversation
Signed-off-by: Dmitry Dygalo <dmitry.dygalo@workato.com>
Stranger6667
force-pushed
the
dd/compiled-schema
branch
from
f2b159b to
1822358
Compare
imor
requested changes
Apr 15, 2026
Contributor
imor
left a comment
imor
left a comment
There was a problem hiding this comment.
Thanks for the PR @Stranger6667. Left a few comments.
Co-authored-by: Raminder Singh <romi_ssk@yahoo.co.in>
Co-authored-by: Raminder Singh <romi_ssk@yahoo.co.in>
Co-authored-by: Raminder Singh <romi_ssk@yahoo.co.in>
Signed-off-by: Dmitry Dygalo <dmitry.dygalo@workato.com>
imor
approved these changes
Apr 15, 2026
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
2 participants
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 introduces a two-level cache for JSON Schema validators including a few public functions +
jsonschemacastWhat is the current behavior?
Currently, validators are re-compiled on every call.
What is the new behavior?
Compiled validators are stored in a per-process LRU cache + per callsite cache
Resolves #88
Some time ago I've read https://www.enterprisedb.com/blog/validating-shape-your-json-data which inspired me to make this PR. Also, it seems like in that comparison they use the debug build :(