Question about setting state from outside state class about blazor-state HOT 4 CLOSED

Ohh that makes sense; I miss understood the tutorial when I went thru it. This is what I was looking for.

from blazor-state.

Hi @david-randoll

The flux pattern is designed to eliminate changes in state by anything other than handlers/reducers. And those handlers are initiated by Actions only. The specific State is encapsulated. All properties should be read-only outside the class. The handlers should be child/nested classes of the state they mutate (this gives the handler access to private setters and thus it can mutate the values)

In the CounterState example the Handler should be a nested class of CounterState.

https://timewarpengineering.github.io/blazor-state/Tutorial.html#handling-the-action

public partial class CounterState // <== this makes it nested in CounterState
{
    public class IncrementCountHandler : ActionHandler<IncrementCountAction>
    {
        public IncrementCountHandler(IStore aStore) : base(aStore) { }

        CounterState CounterState => Store.GetState<CounterState>();

        public override Task<Unit> Handle(IncrementCountAction aIncrementCountAction, CancellationToken aCancellationToken)
        {
            CounterState.Count = CounterState.Count + aIncrementCountAction.Amount; // <== because nested it can access the setters.
            return Unit.Task;
        }
    }
}

Does this clear it up?

from blazor-state.

Yeah, I saw this in the tutorial but didn't like everything being within the state class as this class will become big really quick. If I were to move the IncrementCountHandler class to its own file there's no way to update the counter variable? Thru constructor?

from blazor-state.

@david-randoll By using partial classes, you can have them in the class and in different files. Which is how I do it in the Sample

Hope this helps.

from blazor-state.