Control flow: @for and inline arrays with multiple lines

[cexbrayat]

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

compiler

Is this a regression?

No

Description

It is currently possible to use ngFor with inline arrays:

<div *ngFor="let i of [
  { id: 1 },
  { id: 2 }
]">{{ i.id }}</div>

The current migration properly works, but the generated code is not accepted by the compiler:

@for (i of [
  { id: 1 },
  { id: 2 }
]; track i) {
  <div>{{ i.id }}</div>
}

The compiler fails with the error below

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

NG5002: Parser Error: Missing expected ] at the end of the expression [[] in /Users/cedric/Code/temp/control-flow-errors/src/app/app.component.html@0:6 [plugin angular-compiler]

    src/app/app.component.html:1:6:
      1 │ @for (i of [
        ╵       ~~~~~~

  Error occurs in the template of component AppComponent.

    src/app/app.component.ts:8:15:
      8 │   templateUrl: './app.component.html',
        ╵                ~~~~~~~~~~~~~~~~~~~~~~

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

Angular CLI: 17.0.0-rc.2
Node: 18.18.2
Package Manager: npm 9.7.1
OS: darwin arm64

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

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.0-rc.2
@angular-devkit/build-angular   17.0.0-rc.2
@angular-devkit/core            17.0.0-rc.2
@angular-devkit/schematics      17.0.0-rc.2
@angular/cli                    17.0.0-rc.2
@schematics/angular             17.0.0-rc.2
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.1

Anything else?

No response

[angular-automatic-lock-bot]

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.}