Closed simevo closed 1 year ago
this is a valid fix:
import { Form as VeeForm } from 'vee-validate';
Yep, nothing I can do about that at the moment. The chosen component names are done for simplicity. You will have to rename them to follow that eslint rule like you noted.
What happened?
using vee-validate in Declarative Components mode with the approach outlined in the README conflicts with https://github.com/vuejs/eslint-plugin-vue
Reproduction steps
I enabled the default eslint config for vite:
running
eslint --ext .js,.vue --ignore-path .gitignore --fix src
on this code:triggers the rule
vue/no-reserved-component-names
.Version
Vue.js 3.x and vee-validate 4.x
What browsers are you seeing the problem on?
Relevant log output
Demo link
none
Code of Conduct