eslint-plugin-vue vs vuetify

[icleolion]

Don't suppose anyone has noticed vuetify's usage of v-slot modifiers is invalid according to eslint-plugin-vue's valid-v-slot rule?

Vuetify documentation example -> https://codepen.io/pen/?&editable=true&editors=101=https%3A%2F%2Fvuetifyjs.com%2Fen%2Fcomponents%2Fdata-tables%2F
eslint-plugin-vue rule documentation -> https://eslint.vuejs.org/rules/valid-v-slot.html

Also it isn't happy about the below either, but this i'm not too fussed about:

So who is right and who is wrong, or are you both right and I shouldn't bother creating an issue about it on either of your github repositories? Discuss... 😉

[KaelWD]

Your codepen link is blank, but I'm assuming it's about item.foo slots. eslint-plugin-vue is technically correct, but v-slot is a compiler directive and actually ignores modifiers - v-slot:foo.bar is compiled to scopedSlots: { 'foo.bar' () { ... instead of directives: [{ name: 'slot', arg: 'foo', modifiers: { bar: true } }]

So eslint-plugin-vue is actually wrong here, because this convention does work as expected.

[icleolion]

Bugger would help if I saved the codepen after pushing it out of the documentation!
https://codepen.io/icleolion/pen/ExVJGbv

But anyways, you were right about what I was getting at. I'll log the issue with eslint-plugin-vue then. See if they have a counter argument and send me back your way 😅

EDIT: issue has been logged vuejs/eslint-plugin-vue#1165

[icleolion]

I see @KaelWD is taking this up with the Vue.js team directly now, so I consider this discussion complete as far as Vue 2 is concerned. We shall see how things play out for Vue 3. 🤞

vuejs/core#1241