Changing JSON validator to be able to deal with multiple docs when YAML is treated as JSON #84
Conversation
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
…YAML is treated as JSON
GrantBirki
approved these changes
Apr 15, 2025
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.
This PR changes the JSON validator so that when
yamlAsJson=trueandallowMultipleDocuments=trueall documents within the file are validated with the given schema.yamlAsJsonistruethe data will always be an array; if there's only one doc in the YAML this array will be a length of 1allowMultipleDocumentsis true as well then the data is parsed withparseAllDocuments, otherwise justparse(which is single doc)I hope this PR fulfils the expectations for contributions, otherwise I'd be happy to iterate.
fixes #83