Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to control flow blocks #15333

Open
dkamburov opened this issue Feb 4, 2025 · 0 comments · May be fixed by #14864
Open

Switch to control flow blocks #15333

dkamburov opened this issue Feb 4, 2025 · 0 comments · May be fixed by #14864
Assignees
Labels
🛠️ status: in-development Issues and PRs with active development on them 🧰 feature-request

Comments

@dkamburov
Copy link
Contributor

dkamburov commented Feb 4, 2025

Is your feature request related to a problem? Please describe.

Replace the *ng directives in the templates of the components with the new control flow blocks

Describe the solution you'd like

Main issue comes up when *ngFor is replaced with @for, the new type requires trackBy function and there is a warning from Angular that some the templates are re-creating dom elements, which is a potential issue with performance. So each warning needs to be investigated further.

Additional context

https://github.com/IgniteUI/igniteui-angular/actions/runs/13028614265/job/36342673190?pr=14864

@dkamburov dkamburov linked a pull request Feb 4, 2025 that will close this issue
14 tasks
@damyanpetev damyanpetev added 🛠️ status: in-development Issues and PRs with active development on them and removed 🆕 status: new labels Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠️ status: in-development Issues and PRs with active development on them 🧰 feature-request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants