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
// todos.component.ts
import { ChangeDetectionStrategy, Component, ChangeDetectorRef } from '@angular/core';
import { TodoModel } from './../actions/todo.model';
import { TodosStateActions } from './../actions/todos.actions';
import { signalActions } from '@ng-state/store';
@Component({
selector: 'todos',
templateUrl: './todos.component.html',
changeDetection: ChangeDetectionStrategy.OnPush
})
export class TodosComponent extends HasStateActions<TodosStateActions> {
actions = signalActions(TodosStateActions);
}
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
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:
Starting from v9.5.2 it is possible to use decorator and pass all required params to actions.init method in order to have store injected into actions.