Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More configuration options for vue/no-reserved-component-names #2556

Open
mpiniarski opened this issue Sep 16, 2024 · 0 comments · May be fixed by #2594
Open

More configuration options for vue/no-reserved-component-names #2556

mpiniarski opened this issue Sep 16, 2024 · 0 comments · May be fixed by #2594

Comments

@mpiniarski
Copy link

What rule do you want to change?
vue/no-reserved-component-names

Does this change cause the rule to produce more or fewer warnings?
Fewer

How will the change be implemented? (New option, new default behavior, etc.)?
Change in the existing rule.

Please provide some example code that this change will affect:

export default defineComponent({
  components: {
    Button,
  },
...
});

can be configured to not produce error anymore

What does the rule currently do for this code?
Throws an error when using Button name for component.

What will the rule do after it's changed?
Will not throw an error when using Button name for component. Will still throw an error when using button.

Additional context

Vue seems to be capable to diffrentiate:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant