'v-for' directives require 'v-bind:key' directives.

[ideal123]

• Platform: win10
• Vetur version: 0.8.3
• VSCode version: 1.13.1

'v-for' directives require 'v-bind:key' directives when I use <li class="item-right" v-for="n in 19">{{ n }}</li>.

[ideal123]

[emrekaranfil]

I have with this problem. I did not understand why.

[topul]

In 2.2.0+, when using v-for with a component, a key is now required.

[topul]

but, this is still a bug

[HerringtonDarkholme]

@ideal123 This is intended ESLint feature. You can turn off eslint check in future release. See #235 (comment)

@emrekaranfil Would you mind provide an example repo for this problem? It seems eslint is reporting at wrong location.

@topul This is a valid bug! Ping @mysticatea, any idea? An upstream pull request is already here. vuejs/eslint-plugin-vue#45

[ideal123]

@topul I use v-for with a html element, and a key is unnecessary

@HerringtonDarkholme I disabled ESlint Plugin, but there is the same error.

[HerringtonDarkholme]

@ideal123 ESLint support is builtin with vetur. Please peruse #235. Closing vetur's builtin eslint has already been scheduled.

For the bug in this issue, it has been extracted in #263 and fixed in #264.

So close this issue now.