Angular’s classic change detection is powerful but costly. OnPush helps, but still costly at scale. Signals bring fine-grained updates allowing #Angular to only check views that "really" changed.
TIL that today it is possible to express a generic @typescript function where a parameter with an array of types can be spread into distinc types in a typesafe manner.
https://t.co/RLjdaxzVte
Some secret design sauce — never use gray borders with shadows.
Use a semi-transparent outline instead, so the bottom edge blends with the shadow and gets darker instead of turning into mud.
Subtle, but once you see it you can't unsee it.
Did you know that if you don't rely on JIT compilation, you don't need the platform-browser-dynamic package ?
And in v20, the Angular CLI won't pull it anymore in newly created projects.
Here are the slides from my talk on Micro Frontends in #Angular (including source code), which I gave at Ng-India last week
https://t.co/CntRMHeavG
Finally, huge respect to @debug_mode for running this conference with such dedication, even in the face of occasional headwinds.
Angular Docs will integrate an adapter with the Navigation API (experimental) on the router to improve client side navigation and having navigations to be displayed more fully in the browser UI.
More details here: https://t.co/Skv2yXX4NU
#angular
The resource API is full of neat tricks - did you know you can stream a response, too? This feature and more are available in Angular 19.2
Check the blog post here: https://t.co/Q8KCBkDZES
New in @ChromeDevTools: Accurately emulate CPU performance of a low/mid tier phone with Automatic CPU throttling calibration! 📲
This feature calculates slow-downs for your specific device. Wanted this for years! We just shipped it.
@tomastrajan Testing with change detection and templates is such a pain 🥲 because of it, testing takes me longer to make than the actual implementation itself.
TDD doesn't work for UIs, period.
UI needs to be optimized for flexibility and ease of change
Therefore having any real logic in components, and needing to testing is a losing strategy
The best thing to do is to move ALL logic to headless part of the implementation, eg services of NgRx state slices (selectors, reducers, effects)
Then we don't have to test components as their are logic less, we can change them easily
and it's much easier to test headless impl, as there is no change detection or template
win - ease of change
win - no need to test components
win - easy to test headless, developing headless impl against tests is great DX
Get method caller info in C#
Did you know we can get info about the caller of a method using info attributes?
Have you use info attributes before?
#dotnet