feat: parsing errors #118
Merged
feat: parsing errors #118
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
philsturgeon
suggested changes
Mar 28, 2019
P0lip
force-pushed
the
feat/parsing-errors
branch
from
5894106
to
cbc95a4
Compare
|
@philsturgeon |
philsturgeon
approved these changes
Mar 28, 2019
philsturgeon
pushed a commit
that referenced
this pull request
Mar 28, 2019
* feat: bump @stoplight/yaml * feat: list YAMLExceptions
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
This is post 2.0, most likely :)
Parsing errors are included in validation results.
What is the current behavior?
Parsing errors are ignored.
Other information
(e.g. detailed explanation, related issues, links for us to have context, eg. stackoverflow, issues outside of the repo, forum, etc.)