Flo Edelmann

> The rule should have a list of all `vue` exports and not trigger when the imported value is not one of them (false positive). It will be quite tedious...

Yes, we already have several such update scripts. If you (or someone else) would like to implement this, feel welcome to do so :blush: However, we need to think if...

Hah, looks like we already have that list and update script :sweat_smile: * https://github.com/vuejs/eslint-plugin-vue/blob/master/lib/utils/vue3-export-names.json * https://github.com/vuejs/eslint-plugin-vue/blob/master/tools/update-vue3-export-names.js

Sounds good to me :slightly_smiling_face:

Sounds good, thanks for the suggestion! This should be relatively easy, as we have a reusable function for wrapping core ESLint rules. Would you like to give it a try?...

I don't think we should support [this specific function](https://vueuse.org/core/useVModels/) from VueUse. But we should probably consider all props used when they are passed to a function that is not declared...

Hmm, we already have the [`vue/component-api-style`](https://eslint.vuejs.org/rules/component-api-style.html) rule which allows enforcing one style or another. Maybe we could add a new "consistent" option there and make it the default (as a...

But do note that using both together is actually allowed (albeit not optimal): > You can access Composition-API-exposed values from Options API, but not the other way around. https://vuejs.org/api/composition-api-setup.html#basic-usage

Seems like a good rule to me. Note that it sounds similar to #938, maybe both rules can be combined into one?

@Yhspehy Which version of `eslint-plugin-vue` do you use? Does it work with the latest version?