Title: ## Title: Angular CLI 20.x generates confusing filenames and disables default naming conventions · Issue #30609 · angular/angular-cli · GitHub
Open Graph Title: ## Title: Angular CLI 20.x generates confusing filenames and disables default naming conventions · Issue #30609 · angular/angular-cli
X Title: ## Title: Angular CLI 20.x generates confusing filenames and disables default naming conventions · Issue #30609 · angular/angular-cli
Description: 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 d...
Open Graph Description: 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+...
X Description: 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+...
Opengraph URL: https://github.com/angular/angular-cli/issues/30609
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"## Title: Angular CLI 20.x generates confusing filenames and disables default naming conventions","articleBody":"### Command\n\ngenerate\n\n### Is this a regression?\n\n- [x] Yes, this behavior used to work in the previous version\n\n### The previous version in which this bug was not present was\n\n_No response_\n\n### Description\n\nIn Angular CLI v20+, I observed a major regression from a developer UX point of view.\n\nWhen creating a component using:\n\n```bash\nng g c test-component\n\n\nThe generated files are:\n\ntest-component.ts\ntest-component.html\ntest-component.css\n\nExpected:\n\ntest-component.component.ts\ntest-component.component.html\ntest-component.component.css\n```\n\nWhy It’s a Problem:\nFile naming becomes inconsistent and unclear.\n\nStandard naming like .component.ts, .service.ts, etc., helps in readability, maintainability, and avoids confusion.\n\nMany devs (especially those migrating from Angular 12–15) face this issue.\n\nAngular documentation doesn’t clearly explain why this change was made or how to revert properly.\n\nSuggested Solution:\nEither revert to standard .component.ts naming.\n\nOr clearly document the reason and provide a --classic-naming flag.\n\nLet users choose naming conventions during ng new.\n\n### Exception or Error\n\n\n```\n\n### Your Environment\n\n```text\nPackage Version\n------------------------------------------------------\n@angular-devkit/architect 0.2000.4\n@angular-devkit/core 20.0.4\n@angular-devkit/schematics 20.0.4\n@angular/build 20.0.4\n@angular/cli 20.0.4\n@schematics/angular 20.0.4\nrxjs 7.8.2\ntypescript 5.8.3\nzone.js 0.15.1\n```\n\n### Anything else relevant?\n\nNo ","author":{"url":"https://github.com/niraj125","@type":"Person","name":"niraj125"},"datePublished":"2025-06-26T07:39:50Z","url":"https://github.com/angular/angular-cli/issues/30609"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:9b6baac6-b84b-d25a-361b-2e1e8940aa77 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | ACA8:24645:124101B:181D138:6B01E855 |
| html-safe-nonce | 9445a46d87cc36ee23c1ee7b20b7701f015122d422edd23edee0b594296f0c28 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBQ0E4OjI0NjQ1OjEyNDEwMUI6MTgxRDEzODo2QjAxRTg1NSIsInZpc2l0b3JfaWQiOiI2MTA2OTI2NTgwMjEzMzQ0MzQxIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 8954bfb4df8e4f180dda5eaee745444a49ecf494cb2ac320901a3d3b07bf4559 |
| hovercard-subject-tag | issue:3178151761 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular-cli/30609/issue_layout |
| twitter:image | https://opengraph.githubassets.com/4e3b7a66514d7f9060987c1dd345acc05d0cd8a9ec77d91d35353029ce979a92/angular/angular-cli/issues/30609 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/4e3b7a66514d7f9060987c1dd345acc05d0cd8a9ec77d91d35353029ce979a92/angular/angular-cli/issues/30609 |
| og:image:alt | 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+... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | niraj125 |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular-cli git https://github.com/angular/angular-cli.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 36891867 |
| octolytics-dimension-repository_nwo | angular/angular-cli |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 36891867 |
| octolytics-dimension-repository_network_root_nwo | angular/angular-cli |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width