Support JSON Schema in determineScalarType#2
Open
P0lip wants to merge 1 commit into
Open
Conversation
Author
|
@nulltoken what do you think? |
@P0lip I like it!
Maybe prep up a migration strategy with an optional switch for next major version set to 'Core' by default and warning users that they should test their own use cases with the 'JsonSchema' value (and report weird bugs). And then set 'JsonSchema' as the default for vn+1? Few additional thoughts:
|
nulltoken
reviewed
Jan 21, 2020
| case DetermineScalarSchema.Core: | ||
| return determineScalarTypeForCoreSchema(node); | ||
| case DetermineScalarSchema.Json: | ||
| return determineScalarTypeForJsonSchema(node); |
There was a problem hiding this comment.
throw on default to protect from future mistakes?
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
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.
Will fix stoplightio/spectral#936