fix: align deserialization of restricted strings with standard strings #1413
+124
−1
Conversation
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
kouak
force-pushed
the
fix-empty-list
branch
from
81cd76b to
3f566a7
Compare
kouak
changed the title
Collaborator
|
Hi @kouak, Thank you for your contribution, especially for the tests. |
Contributor
Author
|
It can wait :) |
w666
approved these changes
Jan 1, 2026
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.
This PR aligns the deserialization behavior of restricted strings (e.g., pattern, length) with standard strings.
I updated the logic to normalize the schema name before checking the type. Now, restricted strings are correctly identified and behave exactly like standard strings.
Added a test.
Closes #1412