The Q&A with the Angular team brought new insights and we got new content about Signals Inputs and integrating Signals a in a large codebase.
Ng-Poland: Live Q&A Highlights
The Angular team answered community questions at Ng-Poland, and the full session is available on YouTube. Below are the key points worth remembering.
Learning Angular shouldn't require a deep understanding of RxJs from day one. It's an advanced tool, and eventually, every core feature should function even if a developer chooses not to use RxJs.
Angular intends to preserve its opinionated nature in most cases. However, there are areas where the framework should offer flexibility rather than dictating a single approach.
When it comes to local state management, Signals do come with a strong recommendation from the Angular team.
There's no immediate plan to phase out NgModules. That said, it's not off the table forever.
The future of NgModules hinges on community input. If developers start filing GitHub issues asking why NgModules are still necessary, that might be a sign to consider deprecating them.
The debate between constructor-based and inject()-based dependency injection hasn't reached a conclusion yet.
The constructor approach depends on parameter decorators, which haven't been fully standardized yet. Class-level decorators like @Component and @Injectable have largely settled, as discussed in earlier ng-news episodes, but parameter decorators are back to stage 1 of the standards process.
For now, we'll have to wait and see.
Fresh Reads: Signals Content
Netanel Basal regularly covers upcoming features, and his most recent piece focuses on the Signal Input API slated for Angular 17.1.
Evgeny Tuboltsev's latest article demonstrates how to adopt Signals in a legacy codebase with minimal code changes. He shows a technique where a regular property becomes a getter that internally reads from a Signal.
