Rule proposal: multi-word-component-names

[michalsnik]

We don't have a rule for checking this and it's already in style guide, so it might be a good idea to add it here too :)

More informations here:
https://vuejs.org/v2/style-guide/#Multi-word-component-names-essential

[chrisvfritz]

Note that for .vue files, the file basename without extension should be treated as the name if a name option is not present.

[michalsnik]

But I guess we also want to report this case @chrisvfritz, aren't we?

// Header.vue
{
  name: 'TheHeader',
  ...
}

[chrisvfritz]

@michalsnik Yeah, if a name option is present, the filename should be ignored in this case.

[armano2]

note that executeOnVueComponents is not triggered when 2nd parameter of Vue.component is not an object

[samboylett]

Any news on this?

[theoptz]

any updates?

[gkatsanos]

So we prefer to have to MAKE UP extra words for possibly hundreds of components instead of not using reserved words/html standard elements? This rule is quite.. exotic if I may.

[TheAlexLichter]

This is not ideal for a pages folder which mirrors the URL structure (like nuxt has). Files like index.vue or about.vue should be fine 🙈

[FloEdelmann]

@gkatsanos Please see the reasoning in the Vue Style Guide: https://v3.vuejs.org/style-guide/#multi-word-component-names-essential (Specifically, it mentions "future HTML elements".)

@manniL You can disable this rule selectively for these cases: https://eslint.org/docs/user-guide/configuring/configuration-files#cascading-and-hierarchy or https://eslint.org/docs/user-guide/configuring/configuration-files#configuration-based-on-glob-patterns.