Rhywden
commented
7 months ago Okay, so I found a way to get things going. Works like this: You define your actions, state and reducers completely like normal on the Client.
Then you create a static method to register your Fluxor service on the Client:
public static class CommonServices
{
public static void ConfigureServices(IServiceCollection services)
{
var currentAssembly = typeof(Program).Assembly;
services.AddFluxor(options => options.ScanAssemblies(currentAssembly).UseReduxDevTools());
}
}You call this method in Client/Program.cs like so:
var builder = WebAssemblyHostBuilder.CreateDefault(args);
CommonServices.ConfigureServices(builder.Services);
await builder.Build().RunAsync();and also on the Server like so:
var builder = WebApplication.CreateBuilder(args);
// Add services to the container.
builder.Services.AddRazorComponents()
.AddInteractiveServerComponents()
.AddInteractiveWebAssemblyComponents();
YourBlazorWebApp.Client.CommonServices.ConfigureServices(builder.Services);I didn't find a good place to initialize the store yet. Currently it only gets initialized the first time you hit a Client-side page (like the Counter from the default template):
@page "/counter"
@using YourBlazorWebApp.Client.Store.CounterUseCase
@using Fluxor
@rendermode InteractiveAuto
@inherits Fluxor.Blazor.Web.Components.FluxorComponent
<Fluxor.Blazor.Web.StoreInitializer />
<PageTitle>Counter</PageTitle>
<h1>Counter</h1>
<p role="status">Current count: @CounterState?.Value.ClickCount</p>
<button class="btn btn-primary" @onclick="IncrementCount">Click me</button>
@code {
[Inject]
private IState<CounterState>? CounterState { get; set; }
[Inject]
public IDispatcher? Dispatcher { get; set; }
private void IncrementCount()
{
var action = new IncrementCounterAction();
Dispatcher?.Dispatch(action);
}
}but then it'll work and seemingly won't reinitialize every time you hit this page. The store also doesn't get destroyed if you navigate away.
But registering the service on both sides is essential!
two-thirty-seven
stagep
AndreaEBM
mrpmorris
SethVanderZanden
pjh1974
orosbogdan
janusqa
pingu2k4
WhitWaldo
Now with .NET8 released into production we also have what was formerly called Blazor United, i.e. where there formerly was a strict distinction between Blazor Server and Blazor WASM we now have both in one application.
Problem is that I cannot quite figure out how to get Fluxor to get to work on the "client side". For example,
App.razorsimply does not exist anymore, only on the "server". This here does not work:client/Program.csclient/Pages/Counter.razorwhich yields:
InvalidOperationException: Cannot provide a value for property 'Store' on type 'Fluxor.Blazor.Web.StoreInitializer'. There is no registered service of type 'Fluxor.IStore'.Changing to
InteractiveWebAssemblydoes not change anything about that.So, is there a way forward?