Skip to content

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

Closed
@mpiniarski

Description

@mpiniarski

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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions