RFC Proposes Overhaul of Angular Style Guide
Jeremy Elbourn has published an RFC detailing significant revisions to the Angular Style Guide, which has stayed mostly unchanged for eight years. The proposal focuses on eliminating suffixes such as “Component” from class, file, and variable names, a departure from conventions that have been standard practice for years.
Elbourn, who leads the Angular project as tech lead, has expressed his preference against name suffixes in previous Angular Q&A discussions. The updated guide is likely to make this a key change, and similar naming adjustments are expected to apply to Signals. There has already been active debate about whether the $ suffix, commonly used with Observables, should be adopted for Signals as well.
When it comes to templates, the new guidance will let developers pick between inline and separate template files based on what works best for their specific situation.
The revised style guide is planned to be shorter and more focused, covering only Angular-specific conventions instead of duplicating broader JavaScript or general coding standards.
To keep tooling aligned, angular-eslint will receive updates so that its linting rules match the revised style recommendations.
The RFC is open for community input at this time, and contributors are encouraged to provide feedback. Still, the finalized version might not land in time for the Angular 19 release cycle.
You can find the full RFC here: https://github.com/angular/angular/discussions/58412