blog/new-angular-coding-style

[giscus[bot]]

blog/new-angular-coding-style

Embracing the New Angular: A Fresh Perspective on how to write Angular code.

https://angularexperts.io/blog/new-angular-coding-style?ref=dailydev

[jeanfwl]

Thanks for the blog; I appreciate the knowledge!

I have a question: Do you use readonly in your variable declarations, most for service injection?

I've made it a habit to always include private readonly for my services or any variables that don’t change. Do you think it’s really necessary, particularly for service injection?

[Dozorengel]

I have the same question, please, anybody respond

[SrdjanMilic]

What a great article! Thanks for sharing it.

[Haze272]

Nivek, you have a broken link to your GitHub's account

[Haze272]

mistaken reply

[Haze272]

Nivek, you have a broken link to your GitHub's account

[radekbusa]

When we were migrating some more complex components involving ngOnChanges with checks related to previousValue and currentValue which were later executing side effects, such as writing to backend user settings storage, we had some pretty tough time reimplementing that to Signals, the only thing we came up with was using an effect and assigning previous value to a separate private signal. So in current state of affairs, I wouldn't say that computed or effect (easily) replaces ngOnChanges.
However, the transition from private to ECMAScript private fields inspired me a bunch and thank you for that 😎

[szheleshchenko]

You should get in touch with Jean Meche, one of the Angular team members. In one of his talks, he asked people to share use cases where getting rid of standard lifecycle hooks is not suitable or convenient.

[Sp94dev]

Dude! Assigning effects to a variable changed my life! That’s brilliant because it allows us to extract "React-like hooks" as pure functions and reuse them!