Skip to content

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

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

Closed
xxholly32 opened this issue Jun 12, 2024 · 1 comment
Closed

Comments

@xxholly32
Copy link

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

@ota-meshi
Copy link
Member

I personally agree with you, but vue/component-name-in-template-casing has been changed to uncategorized in the past.
#703
I would like to respect that.
Thank you.

@ota-meshi ota-meshi closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2024
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

No branches or pull requests

2 participants