BlazorWithFluxor VS Fluxor

Note: For demonstration purposes I have hooked in the Blazored.Toast component to pop up a Toast message whenever the CounterState is saved or retrieved, as demonstrated in the previous post in this series. For brevity's sake I'm not including that code in this post, but you can find it all in the project's repository on github.

After all of these steps, the solution should look like this branch of the demo repository.

Before we begin: The code for this blog series can be found on github as shown below. To check your progress for this step of the series, view the 002_Add_Fluxor_Libraries branch.

Take a look at Fluxor! Might be a little bit of a learning curve at first, but you will see how much it reduces the headache in these cases.

Ive been using fluxor in my blazor projects. I love it. https://github.com/mrpmorris/Fluxor

Check out https://github.com/mrpmorris/Fluxor which is an implementation of the react pattern for blazor, similar to redux. If you are used to the concepts of actions and reducers it should be pretty easy for you to get going.

There's a ViewModelComponent where T : IViewModel This ViewModel has to be a state object, meaning part of Fluxor.

Look into using some nuget like Blazor-State or Fluxor to achieve this?

You will probably need to implement a shared state that both components can utilize as their model. This is the type of scenario that Fluxor is designed for. (Not a recommendation, just a reference)

Application state using the Flux pattern with the Fluxor library

Another thing you might like based on your username, lol - I'm using Fluxor in one of my projects and it's pretty good. You'd still foreach loop though your list of items, but create an async "fetch data" request for all your items waiting in a queue to be processed. And you can just add observers when parts of your data are loaded. Makes it pretty easy to fetch batches of data