Lars Nielsen added a new article to his testing series covering the RouterTestingHarness. Signal Inputs are on the horizon, and Jecelyn Yeen gave an overview of Chrome DevTools 1992 and 120.
RouterTestingHarness
Writing tests for components that require access to the route is a challenge. Especially when the documentation for RouterTestingModule or provideLocationMocks doesn't explain those features in detail.
Since 15.2, we have a developer-friendly alternative with the RouterTestingHarness. In his latest article of his Routing Testing Series, Lars Nielsen shows how to use the Harness and how it makes our testing life easier.
Signal Input
The "next big thing" in Angular is the Signal input for components. So inputs of type Signal. It is safe to say that we will get them already in a minor version of Angular 17.
Last week, Matthieu Riegler already posted on X what the code could look like.
By the time of this recording, we also have already a first PR. More information about that will be provided in the next episode.
Chrome DevTools 119 & 120
Jecelyn Yeen presented the changes to Chrome DevTools 119 and 120. Be sure to check it out. There may be one handy new feature for you.
One important topic there is the phasing out of Third-Party Cookies. In Chrome, it starts already next month. DevTools are now equipped with tools to help prepare for that if needed.
https://www.youtube.com/watch?v=SpQ_7yZLaIc
Minor Releases
PrimeNg, a popular UI library, was released in version 17, making it compatible with Angular 17.
https://github.com/primefaces/primeng/releases
The same is true for Ionic, a cross-platform. It went up to 7.6.
Top comments (0)