Update schema to support AJV #297
Merged
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
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.
What does this PR do?
Updates the schema to support JSON Schema Draft 7 which is used in AJV. See forcedotcom/sfdx-core#569
This can be merged at any point and does not need to wait for core changes.
These changes do not affect the current JSEN Draft 4 validation.
(Additional reassurance: The schemas at https://github.com/forcedotcom/schemas are already declaring Draft 7 despite JSEN using Draft 4)
Testing that Draft declaration does not matter
yarn link @salesforce/coreWhat issues does this PR fix or reference?
@W-10818834@