v0.4.0 Fixes #38 and #28 and introduces more 3.1 schema support. #40
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
Added support for missing 3.1 schema properties, however it does not cover the `boolean` case
Also adding in other properties to schema that are missing. Test coverage still needs improving and this is a breaking change to low and high models.
This was referenced Dec 8, 2022
|
LGTM |
|
LGTM too, I'll take some time to upgrade Restish soon. |
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.
v0.4.0Updates thebase.Schemafor both high and low-level models to fix some inaccuracies and introduce missing properties for JSON Schema / v3.1What was added
ifelsethenpropertyNamescontainsminContainsmaxContainsunevaluatedItemsunevaluatedPropertiesdependentSchemaspatternPropertiesWhat changed
DynamicValuewas added as a container for values with differing types. This follows the same pattern established in the low level model.Itemscan now be aSchemaProxyor abool(usingDynamicValue), no longer a slice.Notis also no longer a slice.ExclusiveMinimumandExclusiveMaximumare nowDynamicValuepointers that can be either aboolorint64The
ExclusiveMinimumBoolandExclusiveMaximumBoolproperties have been removed as they are now combined.These are breaking changes, but it does set a standard for how to proceed.