Angular 18🔥 is going to release in May 2024 with the below exciting features.
1. New Angular build system package @angular/build.
2. Default Hybrid change detection mode.
3. Improved content projection .
4. Stable Material 3 components.
5. Supports native async/await when app is zoneless.
6. Supports Node.js v22.
7. Supports Hydration for i18n.
And lot more interesting features are coming in version 18.
1. New Angular build system package @angular/build.
2. Default Hybrid change detection mode.
3. Improved content projection .
4. Stable Material 3 components.
5. Supports native async/await when app is zoneless.
6. Supports Node.js v22.
7. Supports Hydration for i18n.
And lot more interesting features are coming in version 18.
🔥2🫡2
Angular Munich pinned «https://blog.pragmaticengineer.com/software-engineering-salaries-in-the-netherlands-and-europe/»
Most Useful Angular Features You’ve Probably Never Used
#complexity: 🟢🟢⚪️⚪️⚪️⚪️
https://javanoscript.plainenglish.io/most-useful-angular-features-youve-probably-never-used-a64522e747a9
#complexity: 🟢🟢⚪️⚪️⚪️⚪️
https://javanoscript.plainenglish.io/most-useful-angular-features-youve-probably-never-used-a64522e747a9
2.8 million Docker Hub repositories infected with malware or phishing
are your devops team still ignore the upgrades?
or "Testen ist für Leute, die nicht improvisieren können?" 😊
"AS IS"
are your devops team still ignore the upgrades?
or "Testen ist für Leute, die nicht improvisieren können?" 😊
"AS IS"
From #Angular 18.1, we get a new feature allowing you to declare complex variables directly inside the template using @let
Currently, we often create variables inside the template using the 'as' keyword combined with a structural directive: *ngIf="dashboard$ | async as dashboard"
Yet this has some drawbacks 🛑
1️⃣ it's hard to reuse these variables across the template unless you wrap the entire template inside the *ngIf, but this is mostly not what you want.
2️⃣ If you work with numbers and the value is null, using *ngIf="count$ | async as count" will not render anything, and nullish coalescing doesn't work 😢
3️⃣ It's hard to create complex, reusable expressions in your template.
4️⃣ You often need some code duplication in for loops or when you need nested properties multiple times
read more in comments...
Currently, we often create variables inside the template using the 'as' keyword combined with a structural directive: *ngIf="dashboard$ | async as dashboard"
Yet this has some drawbacks 🛑
1️⃣ it's hard to reuse these variables across the template unless you wrap the entire template inside the *ngIf, but this is mostly not what you want.
2️⃣ If you work with numbers and the value is null, using *ngIf="count$ | async as count" will not render anything, and nullish coalescing doesn't work 😢
3️⃣ It's hard to create complex, reusable expressions in your template.
4️⃣ You often need some code duplication in for loops or when you need nested properties multiple times
read more in comments...
🔥1
Angular Munich pinned «https://blog.angular.dev/angular-v18-is-now-available-e79d5ac0affe»
Angular Redirect Function 💡
An interesting new feature was released in Angular v18: you can now configure a redirect function inside your route configurations.
The redirect function gives you access to the queryParams and allows you to inject dependencies into the redirect function. By providing greater flexibility and access to route context, this update empowers developers to create more dynamic and context-aware redirects, ultimately improving the overall user experience in Angular applications.
An interesting new feature was released in Angular v18: you can now configure a redirect function inside your route configurations.
The redirect function gives you access to the queryParams and allows you to inject dependencies into the redirect function. By providing greater flexibility and access to route context, this update empowers developers to create more dynamic and context-aware redirects, ultimately improving the overall user experience in Angular applications.