False invalid v-on rule, eslint

[ghost]

I checked the docs and i am using it correctly.
This is error:

This is warning:

VSCode: 1.28.1
Vetur: 0.13.0
Mac Mojave

[armano2]

can you provide example?

[ghost]

I can't unfortunately. Because it doesn't happen always. This brings the question if i do something wrong but it is fairly simple example. Only difference here is i am inside a component inside another component.
It excepts this syntax btw.

also

but not this.

[ghost]

Extra:
Care the first line too

(very interesting)

[ghost]

I think it throws error because it is reserved keyword. But should throw related error. Actually in this instance should not throw error.
If i change the name it is ok.

What to do?
Shoul i report this eslint repo?

[mysticatea]

You cannot use delete as a variable name because delete is a reserved word in JavaScript. Also, Vue.js will throw a compile error on the reserved word.

https://jsfiddle.net/q7kzrx02/

Now, vue-eslint-parser parses the source code delete, but it's a syntax error because the delete expression requires an argument (e.g., delete obj.a). This is the reason that vue/no-parsing-error said "Unexpected end of expression".
As the result of the parsing error, the attribute @click has no value on AST. This is the reason that vue/valid-v-on said "'v-on' directive requires that attribute value or verb modifiers".

Therefore, @click="delete" is an invalid v-on directive and valid-v-on reports it correctly.
However, maybe we can improve the error message for more understandable.

[ghost]

Thanks for the explanation. I figured that too. But i thought it ends up as object prop and should be ok.

[metheany]

I solved this by just replace other words, Example: deleteSomething