Signal Actions
SignalAction has lower boilerplate and follows Angular future vision. However old state approach is same performance efficient and eas to use
Next we need to tell component that it will use TodoActions
There are cases where state path is dynamic. For example if we are using *ngFor
directive and repeating todo.component
we need to pass not only statePath
but stateIndex
as well because statePath
is todos
and stateIndex
will be n
So final path inside of todo.component
will look like todos[stateIndex]
In this case we will create actions inside ngOnInit
statePath
as well as stateIndex
is passed from parent component like this:
final actions statePath is stored in injected into propert
statePath
after actions beying constructed
stateIndex
can also be set for in cases like when you want to pass item index via URL and want to load state according to it. More documentation on section: Passing list item index via router
You can use new Angular templte syntax
@let
to not repeat signal access
Last updated