Changing the interface INonGenericStateObserver to be able to manage the state of different StateObserver<T> objects

[megafetis]

Example: creating base blazor component with register state function, and unregister when Dispose

[megafetis]

now i have to do this ugly thing:

private ConcurrentBag<INonGenericStateObserver> _states = new();

...

public virtual void Dispose()
{
    _disposeCancellationSource?.Cancel();
    foreach (var item in _states)
    {
        item.GetType().GetMethod("Unregister")!.Invoke(item, [this]);
    }
}

[TheDusty01]

Will reply soon, thanks for your PR!

[TheDusty01]

@megafetis could you elaborate on why this is needed? How does the component look like that uses ConcurrentBag<INonGenericStateObserver> _states ?

[megafetis]

@megafetis could you elaborate on why this is needed? How does the component look like that uses ConcurrentBag<INonGenericStateObserver> _states ?

my case:
base component, uses state, auto unsubscribes on dispose, and so on.

public abstract class AbstractComponent : ComponentBase, IDisposable
{
    private CancellationTokenSource? _disposeCancellationSource;

    protected CancellationToken DisposeToken => (_disposeCancellationSource??=new()).Token;
    private ConcurrentBag<INonGenericStateObserver> _states = new();

    protected void RegisterState<TState>(IStateObserver<TState> state,Action? callback = null)
    {
        state.Register(this, callback ?? StateHasChanged);
        _states.Add(state);
    }
    
    protected void RegisterState<TState>(IStateObserver<TState> state, Func<Task> callback)
    {
        state.Register(this, callback);
        _states.Add(state);
    }

    public virtual void Dispose()
    {
        _disposeCancellationSource?.Cancel();
        foreach (var item in _states)
        {
            item.GetType().GetMethod("Unregister")!.Invoke(item, [this]);
        }
    }
}

derived:

@page "/me"
@inherits AbstractComponent
<PageTitle>My page</PageTitle>

<SomeCode/>

@code {
    [CascadingParameter]
    private CabinetStore Store { get; set; } = null!;
    
    protected override void OnInitialized()
    {
        this.RegisterState(Store.Notifications);
    }

}

in addition, there is actually a convenient opportunity to make sense of the common interface INonGenericStateObserver, isn't it obvious?

[TheDusty01]

Thanks for clarifying. I think the AutoState is solving exactly what you're doing but it is only available for Blazor WASM.

Your PR makes sense anyway, we can move those methods to the non generic interface though

[megafetis]

Thanks for clarifying. I think the AutoState is solving exactly what you're doing but it is only available for Blazor WASM.

Your PR makes sense anyway, we can move those methods to the non generic interface though

Thanks, I hope the changes will be published. I dont not, but AutoState is not working for me in blazor wasm net8. May be i do something wrong. But I'm fine with managing subscriptions to the state manually.

[megafetis]

Hello. When do you plan to post updates?