detect when badly formed YAML causes the multi-document error #58
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
jayspadie
approved these changes
Apr 25, 2019
Member
jayspadie
left a comment
jayspadie
left a comment
There was a problem hiding this comment.
Looks reasonable to me. I assume the document.errors aren't localized, so we can reliably match "end of the stream or a document separator is expected"?
Contributor
Author
|
@jayspadie I didn't see anything in
|
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.
detect when badly formed YAML causes the multi-document error and then give an error on an individual line instead of flagging the entire file.
See: microsoft/azure-pipelines-vscode#219