flux VS Fluxor

So Flux architecture with the concept of Stores, Dispatchers, and Actions came about (from React team), and then Redux (a simplified version of Flux - for juniors by a junior).

Flux Homepage

Then came Flux.

So the basic fundamental of state management is to cache recurring data which is to be passed along a lot of component hierarchy. Input/Props drilling is one the issue where state management methodology like flux comes to resort. A central global store that will act as hydration of data to our components and probably act as single source to truth for many entities in your application.

https://github.com/gaearon/flux-react-router-examplehttp://ianobermiller.com/blog/2014/09/15/react-and-flux-interview/https://github.com/facebook/flux

Throughout the examples and explanations of Flux architecture -- Facebook's counterpart to React -- action type names are referenced as enum constants rather than strings. (See examples at http://facebook.github.io/flux/) I am just looking for an articulation of why this is the preferred method.

Flux. Redux's claim to fame was capturing Flux's functionality in a simpler API.

I'm reading about Flux but the example Todo app is too simplistic for me to understand some key points.

You should look into the Flux architecture pattern. It provides a clear structure for managing application state, and there are libraries out there that implement the pattern that you can use if you don't want to roll your own state management solution.

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