Closed bracyw closed 2 weeks ago
Just transfer any ngFor* to @for.
All ngFor* are replaced with @for.
this explains the difference (or at least @for): https://angular.dev/tutorials/learn-angular/5-control-flow-for (for readability)
https://angular.dev/tutorials/learn-angular/5-control-flow-for (for readability)
check out the link, if you have any questions just ask Wyatt / Reid.
if you use the vscode search bar in the top, you can keyword search with %. example for this: <%ngFor>
No response
Description
Just transfer any ngFor* to @for.
Acceptance Criteria
All ngFor* are replaced with @for.
this explains the difference (or at least @for): https://angular.dev/tutorials/learn-angular/5-control-flow-for (for readability)
Proposed Solution
https://angular.dev/tutorials/learn-angular/5-control-flow-for (for readability)
check out the link, if you have any questions just ask Wyatt / Reid.
if you use the vscode search bar in the top, you can keyword search with %. example for this: <%ngFor>
Mocks
No response