Closed uhfath closed 2 years ago
By any chance, is this an ASP.NET hosted WASM app written in .NETCore 3,1 with server-side rendering enabled?
Are you seeing output from server-side rendering? Fluxor isn't active until after first render.
That's a NET 5 Blazor WASM standalone project.
Can you create a repo I can clone?
Sure, here you go.
I think this is the same issue as was discussed in #226 The state is reduced when you navigate to the page, but not when opening it directly since the actions are queued. You can see that in the console.
Sorry to have taken so long to come back to you, this one slipped my attention.
I've tried your repo and the output in the console is correct.
STATE: http://localhost:13006/counter
MANAGER: http://localhost:13006/counter
ASYNC STATE: http://localhost:13006/counter
ASYNC MANAGER: http://localhost:13006/counter
PARAM STATE: http://localhost:13006/counter
PARAM MANAGER: http://localhost:13006/counter
ASYNC PARAM STATE: http://localhost:13006/counter
ASYNC PARAM MANAGER: http://localhost:13006/counter
I'll close this for now. If you have more information for me then reply here and I will reopen it.
If I'm not mistaking this class is responsible for navigating through actions and monitoring current navigation state. If so, than using
[Inject] private IState<RoutingState> RoutingState { get; set; }
should give me current navigation state. However, when used like this:It gives me this:
Shouldn't they be equal? This is how Fluxor is setup: