Update: upgrade vue-eslint-parser (fixes #36, fixes #56, fixes #96) #116
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.
Thank you for waiting!
I have almost done to rewrite
vue-eslint-parser
. ✨no-parsing-errors
rule. It allows us to catch syntax errors of HTML. Those are opt-in for now since enhancement which increases errors is a breaking change.<template>
a bit. Notable changes are below:element.name
property now. It waselement.startTag.id.name
before.element.namespace
. The value of namespaces are defined in there.VOnExpression
node is added in order to handle vue/no-parsing-error: comma-separated methods #96 correctly.This PR has breaking changes in internal APIs, but the rule behaviors are keeping as is, so I think fine as semver-minor.