GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — ## Title: Angular CLI 20.x generates confusing filenames and disables default naming conventions · Issue #30609 · angular/angular-cli

## Title: Angular CLI 20.x generates confusing filenames and disables default naming conventions #30609

New issue
Copy link
New issue
Copy link
Closed as duplicate
Closed as duplicate
## Title: Angular CLI 20.x generates confusing filenames and disables default naming conventions#30609
Copy link

Description

@niraj125
niraj125
opened on Jun 26, 2025
Issue body actions

Command

generate

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

In Angular CLI v20+, I observed a major regression from a developer UX point of view.

When creating a component using:

ng g c test-component


The generated files are:

test-component.ts
test-component.html
test-component.css

Expected:

test-component.component.ts
test-component.component.html
test-component.component.css

Why It’s a Problem:
File naming becomes inconsistent and unclear.

Standard naming like .component.ts, .service.ts, etc., helps in readability, maintainability, and avoids confusion.

Many devs (especially those migrating from Angular 12–15) face this issue.

Angular documentation doesn’t clearly explain why this change was made or how to revert properly.

Suggested Solution:
Either revert to standard .component.ts naming.

Or clearly document the reason and provide a --classic-naming flag.

Let users choose naming conventions during ng new.

Exception or Error


### Your Environment

```text
Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.2000.4
@angular-devkit/core         20.0.4
@angular-devkit/schematics   20.0.4
@angular/build               20.0.4
@angular/cli                 20.0.4
@schematics/angular          20.0.4
rxjs                         7.8.2
typescript                   5.8.3
zone.js                      0.15.1

Anything else relevant?

No

Reacted by Duc Thang Vu

Activity

  1. alan-agius4
    closed this as a duplicateof CLI: [command new] add option to enable previous suffix generation on create #30594 on Jun 26, 2025
  2. angular-automatic-lock-bot commented on Jul 27, 2025

    @angular-automatic-lock-bot
    angular-automatic-lock-botBot
    on Jul 27, 2025
    More actions

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  3. angular-automatic-lock-bot
    locked and limited conversation to collaborators on Jul 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.