What is the new Route-level render mode introduced in #Angular v19 🤔
If you're using server-side rendering (SSR), by default, Angular will render all parametrized routes on the server and pre-render (also known as "static site generation" or SSG) all routes without parameters. This helps to serve your un-parametrized routes even faster⚡️
But sometimes, you might not want to pre-render the page and always want to render it on the server. Some reasons might be:
🔹 The page content changes based on the user (e.g., user dashboards, personalized recommendations, or profile pages).
🔹 The page displays data that updates frequently and needs to show the most current state, such as stock prices, live sports scores, or news headlines.
🔹 Pages can change based on actions taken in an admin panel (think of products in an e-commerce website; you can change the price, images, etc)
If you're using server-side rendering (SSR), by default, Angular will render all parametrized routes on the server and pre-render (also known as "static site generation" or SSG) all routes without parameters. This helps to serve your un-parametrized routes even faster⚡️
But sometimes, you might not want to pre-render the page and always want to render it on the server. Some reasons might be:
🔹 The page content changes based on the user (e.g., user dashboards, personalized recommendations, or profile pages).
🔹 The page displays data that updates frequently and needs to show the most current state, such as stock prices, live sports scores, or news headlines.
🔹 Pages can change based on actions taken in an admin panel (think of products in an e-commerce website; you can change the price, images, etc)
✨ Dynamically Display a Required Asterisk with #css Only! ✨
There's no need to manually insert an asterisk for required fields in your form. With a touch of CSS magic, it can be done automatically! 😎
This method allows the required asterisk to show up dynamically, saving you both time and effort in your markup. 💪
Codepen: https://codepen.io/syansari02/pen/azovjdV
There's no need to manually insert an asterisk for required fields in your form. With a touch of CSS magic, it can be done automatically! 😎
This method allows the required asterisk to show up dynamically, saving you both time and effort in your markup. 💪
Codepen: https://codepen.io/syansari02/pen/azovjdV
#ToDo for Weekend!
https://yhype.me/
Example for "profile views": https://github.com/DerHerrGammler
https://yhype.me/
Example for "profile views": https://github.com/DerHerrGammler
yhype.me
Ÿ HŸPE
Get to know why the Hype? We gather statistics all over the Universe!
https://www.angularspace.com/always-unsubscribe-no-exceptions-debate-closed/
haha) Dani vs. Deborah..... Let's fight!
haha) Dani vs. Deborah..... Let's fight!
Angular Space
Always unsubscribe. No exceptions. Debate closed.
So many years with Angular.
So many years with RxJS.
Yet people still fight over “when NOT to unsubscribe”.
Truth is. It’s not even worth the conversation.
Just unsubscribe always. Simple.
I have recently posted the same advice on my social media(X/LinkedIn).…
So many years with RxJS.
Yet people still fight over “when NOT to unsubscribe”.
Truth is. It’s not even worth the conversation.
Just unsubscribe always. Simple.
I have recently posted the same advice on my social media(X/LinkedIn).…
This media is not supported in your browser
VIEW IN TELEGRAM
🔥 😯 Angular is introducing a new Change Detection Tracing Service in DevTools that will automatically warn developers when their applications are triggering too many change detection cycles.
In the example when your application exceeds 10 change detections within a 1-second window, Angular will automatically log a warning to help you identify potential performance issues.
👉 PR: https://github.com/angular/angular/pull/58916
In the example when your application exceeds 10 change detections within a 1-second window, Angular will automatically log a warning to help you identify potential performance issues.
👉 PR: https://github.com/angular/angular/pull/58916
🆕 proposal for a JS operator - "::"
The "::" bind operator is still in Stage 0, meaning it's just an early concept being discussed.
It makes method binding and chaining clean, using "this"! ⛓️👇
https://github.com/tc39/proposal-bind-operator
#js
The "::" bind operator is still in Stage 0, meaning it's just an early concept being discussed.
It makes method binding and chaining clean, using "this"! ⛓️👇
https://github.com/tc39/proposal-bind-operator
#js
‼️ `aria-label
👇🏻
https://benmyers.dev/blog/dont-use-aria-label-on-static-text-elements/
#accessibility #a11y
and aria-labelledby` aren't allowed on divs, spans, and most other static text elements out of the box (i.e., without also changing roles), and *most* screenreaders won't announce them.👇🏻
https://benmyers.dev/blog/dont-use-aria-label-on-static-text-elements/
#accessibility #a11y
Ben Myers
Don’t Use aria-label on Static Text Elements
Don’t use the aria-label or aria-labelledby attributes on divs, spans, or other elements representing static/noninteractive text-level semantics, unless you’re also updating roles.
💡 #angular Tip!
Did you know you can format dates, numbers, percentages, and currencies in Angular without relying on pipes? 🚀
👉 Simply call Angular’s built-in formatting functions directly in your code, specifying parameters like the date format or locale.
✨ Why it’s awesome:
• No need for dependency injection (unlike importing DatePipe).
• Easily format data within services or other parts of your code.
• Streamlined, efficient, and perfect for scenarios where pipes aren’t accessible!
A small tweak that can make a big difference in your app’s performance and flexibility. 💻
Did you know you can format dates, numbers, percentages, and currencies in Angular without relying on pipes? 🚀
👉 Simply call Angular’s built-in formatting functions directly in your code, specifying parameters like the date format or locale.
✨ Why it’s awesome:
• No need for dependency injection (unlike importing DatePipe).
• Easily format data within services or other parts of your code.
• Streamlined, efficient, and perfect for scenarios where pipes aren’t accessible!
A small tweak that can make a big difference in your app’s performance and flexibility. 💻
It turns out that this is all standard IEEE 754, which gives a maximum relative rounding error of about 1.11e-16.
In JavaScript, when you compare 100 == 99.99999999999999, it evaluates to false because the precision of the number representation can lead to small inaccuracies. The value 99.99999999999999 is slightly less than 100, causing the comparison to fail.
On the other hand, 100 == 99.999999999999999 evaluates to true because this number is represented in a way that is close enough to 100 within the limits of the floating-point precision defined by IEEE 754. In this case, the tiny difference falls within the acceptable error margin, and thus the two values are considered equal by JavaScript.
This illustrates how floating-point arithmetic can lead to unexpected results in programming!
In JavaScript, when you compare 100 == 99.99999999999999, it evaluates to false because the precision of the number representation can lead to small inaccuracies. The value 99.99999999999999 is slightly less than 100, causing the comparison to fail.
On the other hand, 100 == 99.999999999999999 evaluates to true because this number is represented in a way that is close enough to 100 within the limits of the floating-point precision defined by IEEE 754. In this case, the tiny difference falls within the acceptable error margin, and thus the two values are considered equal by JavaScript.
This illustrates how floating-point arithmetic can lead to unexpected results in programming!
https://blog.angulartraining.com/how-to-run-repeated-http-requests-with-angular-signals-5f66f8db73f8
#angular #signals #rxjs #easy
#angular #signals #rxjs #easy
Medium
How to run repeated HTTP requests with Angular Signals?
A few years ago, I published a tutorial on how to do polling with RxJs and Angular. The goal was to illustrate how to retrieve and render…
🎉 It's that time again! The 2024 Annual Anonymous Salary Survey for Tech Professionals in Germany 🇩🇪 is now live!
It takes just 3 minutes to share your input and help create valuable insights into tech salaries across Germany.
Take the survey and feel free to share it with your colleagues and friends:
👉 https://airtable.com/appbmmHgUzFU3Qres/pagxOj4KVV2pJ7YUZ/form
⏳ Deadline: before 2025 rolls in. Results, along with highlights from 2024, will be shared in January 2025.
In the meantime, check out last year’s analysis: https://ksyula.github.io/Salary-report/
Your participation makes a difference — thank you for contributing to this community effort! Wishing you a joyful holiday season 🎄 and a great start to 2025!
(c) Ksenia Legostay
It takes just 3 minutes to share your input and help create valuable insights into tech salaries across Germany.
Take the survey and feel free to share it with your colleagues and friends:
👉 https://airtable.com/appbmmHgUzFU3Qres/pagxOj4KVV2pJ7YUZ/form
⏳ Deadline: before 2025 rolls in. Results, along with highlights from 2024, will be shared in January 2025.
In the meantime, check out last year’s analysis: https://ksyula.github.io/Salary-report/
Your participation makes a difference — thank you for contributing to this community effort! Wishing you a joyful holiday season 🎄 and a great start to 2025!
(c) Ksenia Legostay
A gentle reminder for software engineers (you'll be thankful):
• Learn SQL before ORM.
• Learn Git before Jenkins.
• Learn SQL before NoSQL.
• Learn CSS before Tailwind.
• Learn Linux before Docker.
• Learn English before Python.
• Learn REST before GraphQL.
• Learn JavaScript before React.
• Learn HTML before JavaScript.
• Learn Containers before Kubernetes.
• Learn Monolith before Microservices.
• Learn Data Structures before Leetcode.
• Learn Server Management before Serverless.
• Learn to ask the Right Questions before ChatGPT.
The bottom line: Learn fundamentals before going deep.
What else would you add?
• Learn SQL before ORM.
• Learn Git before Jenkins.
• Learn SQL before NoSQL.
• Learn CSS before Tailwind.
• Learn Linux before Docker.
• Learn English before Python.
• Learn REST before GraphQL.
• Learn JavaScript before React.
• Learn HTML before JavaScript.
• Learn Containers before Kubernetes.
• Learn Monolith before Microservices.
• Learn Data Structures before Leetcode.
• Learn Server Management before Serverless.
• Learn to ask the Right Questions before ChatGPT.
The bottom line: Learn fundamentals before going deep.
What else would you add?
Hey ppl! I need you! :-)
he-he... I thought, that "ngx-translate" was a long time dead... =) And many devs switched to "transloco"...
What you think... What should I choose @2025 for my "ng new mew"?
he-he... I thought, that "ngx-translate" was a long time dead... =) And many devs switched to "transloco"...
What you think... What should I choose @2025 for my "ng new mew"?