Deserializing ID's from JSON numeric nodes takes constrains into account #374
Conversation
This file contains 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
… should be taken into account.
renzo-baasdam
approved these changes
Feb 14, 2024
Corniel
added a commit
that referenced
this pull request
Mar 27, 2024
…ount (#374) When deserializing from JSON numeric nodes, the constraints of the ID should be taken into account.
Corniel
added a commit
that referenced
this pull request
Apr 19, 2024
…ount (#374) When deserializing from JSON numeric nodes, the constraints of the ID should be taken into account.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When an (numeric) identifier was deserializing, the constraints defined (in
TryCreate) where not triggered.