fix: transform uses placeholderPattern: false #163
Merged
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.
We explicitly disable placeholderPatterns to prevent compilation errors
of valid Vue.js templates using Babel 7 transform.
Please check if the PR fulfills these requirements
yarn lint
)What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
You can see in the failing test case that a valid Vue.js template is not compiled successfully if it has all caps alone between two-tags. Babel transform assumes this is the start of a placeholder pattern unless it is explicitly told not to do that.
What is the new behavior?
Valid Vue.js templates are always compiled.
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
This issue is referenced here:
babel/babel#8067