fix: DynamicValue in high model schema missing N value #72
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.
Found a small issue while upgrading to the latest libopenapi. The new
DynamicValue.N
field is not copied over from the low-level model, so for exampleschema.ExclusiveMinimum.IsB()
will always returnfalse
. This PR fixes it and adds a small test to assert the values get set. For the boolean case it is left alone asN
will default to zero.Note: this is important as the exclusive minimum can be zero, in which case it's currently not possible to determine whether a value was set or which one was set.
Sorry for the delay in upgrading BTW, I got side-tracked shipping https://rest.sh/#/bulk