Talks about modifying the effect function kicked off last week. Paul Gschwendtner released a piece covering Signal Inputs, while Joshua Morony shared his own write-up on working with ChatGPT.
effect() and potential changes
Even in Angular 17, Signals cannot be regarded as entirely stable — the effect() function remains in developer preview. A GitHub issue now exists where Alex Rickabaugh of the Angular team clarifies the unique circumstances surrounding effect().
Consider a scenario where an effect renders a fresh View that depends on Signals; the effect will then respond to updates in those Signals as well. This could produce behavior you might not have anticipated.
The Angular team is currently deliberating on how to handle cases like these. One option under discussion is the framework abstaining from tracking Signals in such or comparable contexts.
For the present, there's a manual escape hatch: the untracked() function, which needs to be placed inside the effect.
https://github.com/angular/angular/issues/54548#issuecomment-1957841038
Signal Inputs
Paul Gschwendtner from the Angular team was instrumental in bringing Signal Inputs to life and authored an article on the topic. His piece laid out the advantages over the legacy @Input() decorator, complete with numerous code examples illustrating various scenarios.
Signal Inputs are still labeled as developer preview, and the Angular team is actively seeking input. They're particularly interested in hearing about any confusion caused by the syntax, or problems arising from the mandatory read-only nature that comes with the Signal type.
Developing with ChatGPT
For those who incorporate or depend on AI in their everyday coding workflows:
Joshua Moronoy recounted his experience with ChatGPT, detailing his struggle to strike a balance between leveraging the AI as a helpful aide while retaining control, versus leaning on it entirely and hitting a plateau in his own growth.