wip: support empty and recursive schemas #496
Closed
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.
The main contribution of this PR is an enhanced
to_regex
function, which addresses both empty and recursive JSON schemas. I utilize the capabilities of theregex
library, which notably supports recursion. Here's how this is achieved:Handling Empty JSON Schemas
We identify empty schemas (i.e.,
{}
orTrue
) as those that should accept any valid JSON. To achieve this, a specific regex pattern for JSON values is implemented. This pattern is designed to be universally accepting.Addressing Recursive JSON Schemas
The core of handling recursion lies in the use of named capture groups within the regex patterns. These groups are critical for creating references within the regex that can call back to themselves or to other groups.
The
regex
library's support for recursion is fundamental to this approach. It allows for patterns that can reference themselves, enabling the definition and validation of recursive and self-referential schemas. This is particularly important for complex schemas where elements may be nested within themselves or have mutual references.