add_action('wp_head', function(){echo '';}, 1);{"id":3821,"date":"2025-01-28T01:20:23","date_gmt":"2025-01-28T01:20:23","guid":{"rendered":"https:\/\/santiceramics.com\/?p=3821"},"modified":"2025-11-06T19:31:13","modified_gmt":"2025-11-06T19:31:13","slug":"results-in-60-seconds-2","status":"publish","type":"post","link":"https:\/\/santiceramics.com\/?p=3821","title":{"rendered":"Results in 60 seconds!"},"content":{"rendered":"

A complete guide to all the features of the @if template syntax, including the most frequently asked questions bout this syntax, as well as an anti-pattern to avoid. A complete guide to all the features and best practices of the new @for template syntax, as well as a full explanation of the now mandatory tracking function. This has to do with the usage PowerTrend<\/a> of the @if syntax not really to show or hide an element, but just to access the values of an observable using the async pipe. This is because the @if syntax is part of the template engine itself, and it is not a directive. We will compare the two syntaxes, and explain why the new @if syntax is better and how to automatically migrate to it. If the observable is a HttpClient call,it\u2019s important to use the async pipe only once, otherwise you get multiple network calls.<\/p>\n