Jeremy Elbourn’s new RFC outlines key updates to the Angular Style Guide, including removing suffixes like “Component” from class, file, or variable names. The guide will be more concise, focusing on Angular-specific practices, with angular-eslint rules updated accordingly.
Jeremy Elbourn, the tech lead of the Angular project, recently shared an RFC proposing an essential update to the Angular Style Guide, which has remained largely the same for eight years.
Jeremy has previously voiced in Angular Q&A sessions that he’s not a fan of adding suffixes like “Component” to class, file, or variable names. As such, the removal of suffixes and similar naming conventions is expected to be one of the major updates in the Style Guide. This approach also extends to Signals, where there has been ongoing discussion about whether to adopt the $ suffix convention used for Observables.
For templates, developers will have the flexibility to choose between inline and separate templates based on their preferences.
The updated Style Guide is anticipated to be more concise, focusing exclusively on Angular-specific practices rather than covering general best practices.
Additionally, angular-eslint will be updated to ensure linting rules are consistent with the new style guidelines.
The RFC is currently open for community feedback, so contributors are encouraged to share their thoughts. However, the final version may not be ready in time for Angular 19.
Link to the RFC: https://github.com/angular/angular/discussions/58412
Top comments (0)