Closed adcentury closed 5 years ago
Thank you for the report.
But I couldn't reproduce it on our online demo.
@mysticatea This demo's version is not same with my env. Maybe it's the reason.
Please try eslint-plugin-vue@next
@adcentury and let us know if you still have this issue :)
Closing for now. Feel free to reopen if you're still having this problem.
<template>
<Row class="row">
<Col v-for="(tpl, idx) in tplList" :key="tpl.id">
<Card
:id="tpl.id"
:index="idx"
></Card>
</Col>
</Row>
</template>
<script>
export default {
}
</script>
I can reproduce the issue with the code above. Problem will disappear when changing <Col>
to <div>
, which is:
<template>
<Row class="row">
<div v-for="(tpl, idx) in tplList" :key="tpl.id">
<Card
:id="tpl.id"
:index="idx"
></Card>
</div>
</Row>
</template>
<script>
export default {
}
</script>
Here is the online demo.
The <Col>
element is recognized as an HTML <col>
element.
Since the HTML <col>
element is a void element, it is treated as if there are no internal elements.
Also, </col>
will cause a parsing error as an invalid end tag.
Please rename the <Col>
component.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/col
Tell us about your environment
^4.15.0
^4.0.0
10.11.0
Please show your full configuration:
What did you do?
What did you expect to happen? Pass the lint.
What actually happened?