[Feature Request] apply existing rules on aliased components (e.g. <my-btn>)

[azygis]

With createVuetify it's possible to specify aliases for virtual components. Is it possible to configure this plugin to use aliases as well?

[J-Sek]

Yes, you can rely on pnpm patch or patch-package. I use it for some time and works like a charm.

1. open package code in second editor e.g. code node_modules/eslint-plugin-vuetify
2. edit whatever you want
3. run ESLint: Restart ESLint Server in VSCode or restart IDE if it does not have equivalent command
4. verify it applies new rules
5. npx patch-package eslint-plugin-vuetify

Hint for the props rules:

• auto-remove props with empty string
  • e.g. persistentHint: '',
• auto-rename prop
  • e.g. label: 'text',
• mark as deprecated
  • e.g. textColor: false,

This method does not count as "support" for custom rules, but is honestly very easy and does not require forking the repo.

[azygis]

Seems like I worded this poorly.

What I meant is to use the same rules as built-in fixes for aliased components, e.g. specifying alias VUserDataTable: VDataTableServer would report/fix whatever rules specified on VDataTableServer when it encounters VUserDataTable.

I see custom deprecations in 37bb71f that closed the issue, but it's a completely separate functionality from the intent in this one. At least, not without reinventing the whole ruleset, unless I missed some quickhack in there.