DESCRIPTION

It is undisputed that Signals will shape the future of Angular. At first glance, Signals may seem very easy to use — like simple objects with getters and setters. However, you will encounter several pitfalls if you use them this way.

To avoid such situations, we discuss some effective rules of thumb and reactive helpers for using Signals.

You will be surprised by the difference these three rules and helpers can make!

KEY TAKEAWAYS

• Use compute for preventing Signal writes

• Use compute for establishing a reactive data flow

• Effects allow rendering stuff that CANNOT be rendered via data binding

• Do not propagate state via Effects

• Reactive helpers make your code safer and easier to maintain

• Take care of race conditions

• Stores help to streamline the reactive data flow

About MANFRED

Trainer and Consultant with focus on Angular. Google Developer Expert (GDE) for Angular who writes for O'Reilly, the German Java Magazine and windows.developer. Regularly speaks at conferences.