Skip to content

Should vue/component-name-in-template-casing be classified as Essential #2474

Closed as not planned
@xxholly32

Description

@xxholly32

What rule do you want to change?

Should vue/component-name-in-template-casing be classified as Essential

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

more

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

Adjustment classification

Please provide some example code that this change will affect:

/* ✗ BAD */
<el-button>Add ToDo</el-button>
/* ✓ GOOD */
<ElButton>Add ToDo</ElButton>

What does the rule currently do for this code?

https://vuejs.org/style-guide/rules-essential.html#use-multi-word-component-names

What will the rule do after it's changed?

Additional context

I think a lot of the code will be tweaked because so many components are named using multi-word. But this is an official recommendation why not categorize it in Essential Or am I wrong about the rule

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