Rule proposal: `require-component-name`

Please describe what the rule should do:

This rule warns you if the component’s name property is undefined

What category of rule is this?

[x] Enforces code style [ ] Warns about a potential error [ ] Suggests an alternate way of doing something [ ] Other (please specify:)

Provide 2-3 code examples that this rule will warn about:

// bad
export default {
  render(){
    return <div />
  }
}

// good
export default {
  name: 'div-component',
  render(){
    return <div />
  }
}

Why should this rule be included

Naming components is a good practice. It makes it easier to debug your code with Vue Devtools, and helps you to keep your code organized. So much so that at least 2 rules on the Style Guide address the issue of how to name your components - one of them is a essential rule.

[LinusBorg]

The name is necessary when rendering a component recursively.

[chrisvfritz]

Hmm, I would probably leave this out of the style guide and keep it in the uncategorized section here, because a name option is not actually useful in the vast majority of cases. For example:

• When registering a component locally, as the Vue devtools will use the component’s local name.
• When registering a component globally, as providing a name is part of that process.
• When importing a .vue component to be used in a render function, as a name will be derived from the __file property that’s added to the default export.

So now that I think about it actually, and especially since functional components can now be written in .vue files, I can’t think of a real use case where a component needs the name option to be specified. Did I miss any common (or even uncommon) scenarios?