GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — ## Title: Angular CLI 20.x generates confusing filenames and disables default naming conventions · Issue #30609 · angular/angular-cli Closed as duplicate Closed as duplicate Copy link DescriptionCommandgenerate Is this a regression?
The previous version in which this bug was not present wasNo response DescriptionIn 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: 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: Or clearly document the reason and provide a --classic-naming flag. Let users choose naming conventions during ng new. Exception or ErrorAnything else relevant?No Reacted by Duc Thang Vu Activity
MetadataMetadataAssigneesLabelsNo labels TypeProjectsMilestoneRelationshipsDevelopmentIssue 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. |