Skip to content

Angular Material Form Unexpected Behavior After Control Flow Migration #52277

@swami-sanapathi

Description

@swami-sanapathi

Which @angular/* package(s) are the source of the bug?

core

Is this a regression?

No

Description

After running the new control flow migration ng generate @angular/core:control-flow , we encountered unexpected behavior with an Angular Material form component.

Please provide a link to a minimal reproduction of the bug

https://github.com/swami-sanapathi/test-control-flow-migration

Please provide the exception or error you saw

No response

Please provide the environment you discovered this bug in (run ng version)

Angular CLI: 17.0.0-next.9
Node: 18.16.0
Package Manager: npm 9.5.1
OS: win32 x64

Angular: 17.0.0-rc.0
... animations, cdk, common, compiler, compiler-cli, core, forms
... material, platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.0-next.9
@angular-devkit/build-angular   17.0.0-next.9
@angular-devkit/core            17.0.0-next.9
@angular-devkit/schematics      17.0.0-next.9
@angular/cli                    17.0.0-next.9
@schematics/angular             17.0.0-next.9
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.0

Anything else?

No response

Metadata

Metadata

Labels

area: coreIssues related to the framework runtimecore: control flowIssues related to the built-in control flow (@if, @for, @switch)

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions