⭐️ New: Add rule no-reserved-component-names

[shadskii]

This rule addresses #486 and prevents name collisions with vue component and standard html elements. Both PascalCase names and kebab-case names of standard html elements are invalid. For example, 'div' and 'Div' are both treated as reserved names.

[ota-meshi]

@shadskii Thank you for this PR!

I have some requests.

[ota-meshi]

LGTM! Thank you!

[shadskii]

I've added warnings for locally registered components as @michalsnik suggested in #486.
For example:

export default {
  components: {
    'font-face': {},
  }
}

Thanks for the suggestion!

[Mouvedia]

The nobr, strike and acronym tags are missing from this list.

[shadskii]

The nobr, strike and acronym tags are missing from this list.

Originally, I chose to only check for non-obsolete elements. nobr, strike and acronym are all obsolete (see their MDN reference nobr, strike, and acronym ). You bring up a good question: Should we check for obsolete or deprecated tags? I'm inclined to believe the answer is yes. Browsers still render deprecated tags and this will result in a name collision if a vue component shares the same name.

MDN lists 31 obsolete and deprecated elements (see this list). I have added deprecated-html-elements.json with these elements and updated this rule to search for them.

Thank you for reviewing this pull request and please let me know if you agree with the updates I've made!

[Mouvedia]

I'm inclined to believe the answer is yes.

I agree as well, but I wanted to illustrate the need with elements that are obsolete but still heavily exploited nowadays.

Thank you for reviewing this pull request and please let me know if you agree with the updates I've made!

These were merely comments. I didn't review your code nor do I have the time to.
Thank you for the PR.

[vue-bot]

Hey @shadskii, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚