Question: does this library support using C# records for State?

[josephr5000]

Can I do this:

[FeatureState] public record MyState(int balanceA= 0, int balanceB);

such that I could write a reducer:

[ReducerMethod] public static MyState ReduceBalanceChangeA(MyState state, BalanceChangeAAction action) =>
    state with { balanceA = state.balanceA + action.balanceChange };

[mrpmorris]

You either need to write it in its expanded form (like a class) so you can either add a parameterless constructor or a static method to create a default instance, or you could remove [FeatureState] and add a class

public class MyStateFeature : Feature { override the abstract method to create a default state + specify its name }

[uhfath]

Could you please elaborate a bit why we shouldn't use records? Is it because of #274 ?

[uhfath]

Sorry, my bad. I missed the part about "expanded form". So I guess it's safe to use a record like this?

[FeatureState]
public record AuthState : LoaderStateBase
{
    public bool IsAuthorized { get; init; }
    public string UserName { get; init; } = "none";
}

Considering that these defaults are suitable.

[mrpmorris]

Yes, you can also do this

[FeatureState]
public record AuthState(bool IsAuthorized, string UserName)
{
  private AuthState() => new AuthState(false, "None");
}