-
-
Notifications
You must be signed in to change notification settings - Fork 679
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
Rule proposal: component-name-in-template-casing
#250
Comments
component-name-casing
component-name-in-template-casing
I'm sorry. I made a mistake in refs at PR 402 m(_ _)m |
It shouldn't be the default: |
@Mouvedia, It should https://vuejs.org/v2/style-guide/#Component-name-casing-in-templates-strongly-recommended |
@probil The rule is called
Why? Because using PascalCase in SFC and kebab-case everywhere else would be inconsistent: we should recommend and support a solution that doesn't require to make that distinction. |
@Mouvedia Agree with you.
This plugin tries to follow official Vue Style Guide so |
It depends on what matters the most to you:
Both are valid options and have CONs/PROs. |
Style guide:
https://vuejs.org/v2/style-guide/#Component-name-casing-in-templates-strongly-recommended
Description:
This rule would ensure proper component names in templates. As we only check
.vue
files in terms of templates we can provide both options:kebab-case
andPascalCase
Good examples:
Bad examples:
and obviously with
kebab-case
option it would warn aboutPascalCase
and vice-versa.Default option would be
PascalCase
.The text was updated successfully, but these errors were encountered: