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.
Q&A Session at Ng-Poland
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 hosted a Q&A session with seven members of Angular. The recording is available on YouTube, and here are the main takeaways.
RxJs should be optional to start learning Angular. It is an advanced feature, and in the future, it should also be possible to use all the critical functions without RxJs.
Angular wants to stay opinionated as it used to. In certain areas, where the framework doesn't need to provide "one way how to do things", it should be possible to be more individual.
With Signals, Angular is quite opinionated regarding local state management.
There are no plans to deprecate NgModules. That doesn't mean it will never happen.
The decision depends entirely on the community. If GitHub issues are popping up, where developers do not understand the need for NgModules anymore, it might be time to start thinking about sending them (NgModules) to retirement.
There is no final answer in the discussion between constructor vs. inject-based dependency injection.
The constructor version relies on parameter decorators, which are currently standardised. As explained in former episodes of ng-news, the standardisation for class-based decorators (like @Component, @Injectable) is more or less done. Parameter decorators have been set back to stage 1.
At the moment, we still have to wait.
Articles
Netanel Basal quite often publishes articles on upcoming features. His latest is about the Signal Inputs for Angular 17.1.
Evgeny Tuboltsev published an article explaining how to integrate Signals into a legacy application without changing much code. He's applying a technique where a property is replaced by a getter method, which internally calls a Signal.
Top comments (0)