ionic-team / ionic-team/ionic-framework

Question: New Style guide Angular v20.

Open
#30,909 0 comments 1 reaction 0 assignees View on GitHub
triage
Dominant language
TypeScript
Stars
52.7k
Forks
13.3k
Avg merge
1d 15h
Merged PRs (30d)
51

Description

Hi,

With the recent Angular style guide updates (Angular v20), Angular is moving away from enforcing file suffixes like .component and .service, encouraging more flexible and domain-driven naming conventions. [Style guide updates Angular v20](https://blog.angular.dev/announcing-angular-v20-b5c9c06cf301)

Given that Ionic currently relies heavily on conventions such as .page, .page.html, etc., I wanted to ask:

Are there any plans to align Ionic’s file naming conventions with Angular’s updated style guide?

Do you foresee Ionic continuing to recommend .page as a required suffix, or becoming more flexible/optional in the future?

Will the Ionic CLI or schematics adapt to support projects that follow the new Angular “no-suffix” approach?

Thanks in advance, and great work as always

Contributor guide

Open the contributing guide

Research direction

Read the linked Angular v20 style guide update and compare its naming guidance with Ionic's current .page and .page.html conventions. Investigate whether the Ionic CLI or schematics are named as affected entry points; done would require a documented decision about suffix recommendations and future CLI or schematic support.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.