Naming Guidelines (Y120)

[EmmanuelDemey]

• Use consistent names for all components following a pattern that describes the component's feature then (optionally) its type. My recommended pattern is feature.type.js. There are 2 names for most assets:

  • the file name (avengers.controller.js)
  • the registered component name with Angular (AvengersController)

  Why?: Naming conventions help provide a consistent way to find content at a glance. Consistency within the project is vital. Consistency with a team is important. Consistency across a company provides tremendous efficiency.

  Why?: The naming conventions should simply help you find your code faster and make it easier to understand.

[tilmanschweitzer]

+1

[tilmanschweitzer]

Hi, I'm working on a solution.

https://github.com/tilmanpotthof/eslint-plugin-angular/tree/issue-56/Naming-Guidelines-Y120

So far I have a typeSuffix option to specify if and how the component type should be defined. The example in the issue does not match completely my approach, but I will fix that.