{"id":693,"date":"2023-11-28T03:48:00","date_gmt":"2023-11-28T03:48:00","guid":{"rendered":"https:\/\/staging.infragistics.com\/blogs\/?p=693"},"modified":"2025-02-19T07:13:50","modified_gmt":"2025-02-19T07:13:50","slug":"control-flow-in-angular-17","status":"publish","type":"post","link":"https:\/\/www.infragistics.com\/blogs\/control-flow-in-angular-17","title":{"rendered":"Control Flow In Angular 17: Elevate Your Development Experience"},"content":{"rendered":"\n

I’m excited to share that you can enhance your Angular development experience within Ignite UI for Angular<\/a> components by embracing the new Block Template Syntax for optimized, built-in control flow. This powerful feature simplifies your code, improves type checking, reduces bundle size, and boosts performance. So now, let’s dive into some code samples to see the syntax in action!<\/p>\n\n\n\n

Try Ignite UI for Angular<\/a><\/p>\n\n\n\n

What Is Built-in Control Flow in Angular?<\/h2>\n\n\n\n

The term “Control Flow” in Angular refers to the order in which statements and directives are executed within an Angular application. In Angular 17, there is a new optimized built-in syntax to manage the control flow (@if, @switch, @for), offering developers finer control over the execution flow. This brings developers closer to familiar patterns in most programming languages, minimizing errors in constructing application views. It is directly available and ready to use in templates without additional imports.<\/p>\n\n\n\n

In Angular 17, Control Flow is managed by the refined change detection system, efficiently applying application state changes to the view. This underscores Angular’s role as a provider of a solid foundation for building modern, interactive web applications.<\/p>\n\n\n\n

Starting Off With Conditional Statements <\/h2>\n\n\n\n

What you need to do is upgrade your *ngIf and *ngSwitch with the new syntax for a more intuitive and cleaner code. <\/p>\n\n\n\n

@if<\/p>\n\n\n\n

Utilize the @if within an IgxColumn template of the IgxGrid for conditional rendering: <\/p>\n\n\n\n

<igx-column field=\"Discontinued\" header=\"Discontinued\" [sortable]=\"true\" [dataType]=\"'boolean'\"> \n    <ng-template igxCell let-cell=\"cell\" let-val> \n        @if (val) { \n            <img src=\"assets\/active.png\" title=\"Continued\" alt=\"Continued\" \/>\n        } @else { \n            <img src=\"assets\/expired.png\" title=\"Discontinued\" alt=\"Discontinued\" \/> \n        } \n    <\/ng-template> \n<\/igx-column> <\/pre>\n\n\n\n
Demo @if in IgxColumn<\/a><\/p>\n\n\n\n
@switch <\/p>\n\n\n\n
Apply @switch directive within an IgxSelectItem of the IgxSelect component for dynamic icon selection: <\/p>\n\n\n\n
<igx-select-item [value]=\"fruit.type\" class=\"select__entry\" [text]=\"fruit.type\">\n    {{fruit.type}}\n    @switch (fruit.delivery) {\n    @case ('flight') { <igx-icon>flight<\/igx-icon> }\n    @case ('train') { <igx-icon>train<\/igx-icon> }\n    @case ('boat') { <igx-icon>directions_boat<\/igx-icon> }\n    }\n<\/igx-select-item><\/pre>\n\n\n\n
Demo @switch in IgxSelect<\/a><\/p>\n\n\n\n
Let’s Talk About The Built-In for Loop Next<\/h2>\n\n\n\n
Experience a faster rendering speed with the new built-in for loop.<\/p>\n\n\n\n
@for <\/p>\n\n\n\n
A lot of use cases can be figured out with this. The example here uses the IgxDropDown:<\/p>\n\n\n\n
@for (town of towns | startsWith:townSelected; track town.name) {\n    <igx-drop-down-item [value]=\"town\">\n        {{town}}\n    <\/igx-drop-down-item>\n}<\/pre>\n\n\n\n
Demo For Loop in IgxDropDown<\/a> <\/p>\n\n\n\n
Or looping the columns of the grid: <\/p>\n\n\n\n
@for(c of columns; track c.field) {\n    <igx-column\n    [field]=\"c.field\"\n    [header]=\"c.field\"\n    [cellStyles]=\"c.cellStyles\">\n    <\/igx-column>\n}<\/pre>\n\n\n\n
Demo For Loop in IgxGrid<\/a> <\/p>\n\n\n\n
Deferrable Views for Lazy Loading <\/h2>\n\n\n\n
Leverage the new deferrable views to enhance lazy loading with a declarative and powerful approach. This new feature can give you the ability to create a deferred loading of the list items of the IgxList components. They will appear after a button click: <\/p>\n\n\n\n
<igx-list #fruitList>\n    @defer (on interaction(b1)) {\n        @for(fruit of fruitsData; track fruit) {\n            <igx-list-item igxRipple igxRippleTarget=\".igx-list__item-content\">\n                {{ fruit }}\n            <\/igx-list-item>\n        }\n    } @placeholder {\n        <button #b1 type=\"button\" igxButton=\"raised\">Click here to trigger interaction<\/button>\n    }\n<\/igx-list><\/pre>\n\n\n\n
Demo deferrable view with IgxList<\/a> <\/p>\n\n\n\n
Combined Sample <\/h2>\n\n\n\n
If you want, you can explore a more comprehensive example<\/a> that integrates all the mentioned features. Here, we can defer the main content of the nav drawer. It will be loaded right after an item from the nav is selected: <\/p>\n\n\n\n
@defer(on interaction(drawer)) {\n  <span igxButton=\"icon\" igxToggleAction=\"navigation\">\n    <igx-icon family=\"material\">menu<\/igx-icon>\n  <\/span>\n  <h5>{{selected}}<\/h5>\n  @switch(selected) {\n    @case('Grid') {\n      <app-grid-adf-style-sample><\/app-grid-adf-style-sample>\n    }\n    @case('Autocomplete') {\n      <app-autocomplete><\/app-autocomplete>\n    }\n    @default {\n      <app-reactive-form-validation><\/app-reactive-form-validation>\n    }\n  }\n} @placeholder {\n  <span>Pick a component from nav drawer to load...<\/span>\n}<\/pre>\n\n\n\n
You can check out the network tab to see the application’s initial load time and resources. Since we are deferring the main content of the nav drawer, this is what is loaded:  <\/p>\n\n\n\n
\"control<\/figure>\n\n\n\n
<\/p>\n\n\n\n
And once the user selects an item, the content and the resources for the view are being loaded: <\/p>\n\n\n\n
\"<\/figure>\n\n\n\n
<\/p>\n\n\n\n
Depending on the size of the deferred views, you can increase your load time dramatically. More information on deferred views can be found here<\/a>.  Also, the listing of the nav items can be achieved with the new syntax:<\/p>\n\n\n\n
@for(item of navItems; track item.name) {\n  <span igxDrawerItem igxRipple (click)=\"navigate(item)\">\n    <igx-icon family=\"material\">{{ item.name }}<\/igx-icon>\n    <span>{{ item.text }}<\/span>\n  <\/span>\n}<\/pre>\n\n\n\n
Also, in one of the views from the sample there are reactive form inputs that are utilizing this feature to show the validations, icons and hints: <\/p>\n\n\n\n
<igx-input-group>\n    <label igxLabel for=\"password\">Password<\/label>\n    <input igxInput name=\"password\" [type]=\"showPassword ? 'text' : 'password'\" formControlName=\"password\" \/>\n    @if (password.errors?.minlength) {\n        <igx-hint >Password should be at least 8 characters<\/igx-hint>\n    }\n    @if (password.value) {\n        <igx-icon igxSuffix (click)=\"showPassword = !showPassword\">\n            {{ togglePasswordVisibility }}\n        <\/igx-icon>\n    }\n<\/igx-input-group><\/pre>\n\n\n\n
Getting Started <\/h2>\n\n\n\n
Upgrade your Angular project to version 17 and try out the built-in control flow today. To use it in your existing projects. Explore the improved developer experience and boost the performance of your Angular application.  <\/p>\n\n\n\n
Happy coding with the enhanced Angular control flow!<\/p>\n\n\n\n
\"Ignite<\/a><\/figure>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Do you want to elevate your development experience with Ignite UI for Angular? Try the new block template syntax for optimized, built-in control flow.<\/p>\n","protected":false},"author":64,"featured_media":1002,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-693","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-angular"],"_links":{"self":[{"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/posts\/693","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/users\/64"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/comments?post=693"}],"version-history":[{"count":4,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/posts\/693\/revisions"}],"predecessor-version":[{"id":1919,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/posts\/693\/revisions\/1919"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/media\/1002"}],"wp:attachment":[{"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/media?parent=693"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/categories?post=693"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infragistics.com\/blogs\/wp-json\/wp\/v2\/tags?post=693"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}