Fluxor VS redux

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

I'd like my React based SPA to render on server side (who's not these days). Therefore I want to combine React with react-router, redux and some build layer like isomorphic starterkit.

I have a application structure that mostly mimics the redux real-world example but can't get past getting this error:

In the todoMVC example of the redux project, the reducer for dealing with todos have these lines:

For a while now I've been wracking my brain as to how you would implement undo / redo in Redux with server interactions (via ajax).

{ "name": "add-projects", "version": "0.0.0", "description": "Add projects", "scripts": { "start": "node server.js" }, "repository": { "type": "git", "url": "https://github.com/rackt/redux.git" }, "license": "MIT", "bugs": { "url": "https://github.com/rackt/redux/issues" }, "homepage": "http://rackt.github.io/redux", "dependencies": { "immutable": "^3.7.6", "react": "^0.14.0", "react-dom": "^0.14.0", "react-redux": "^4.0.0", "redux": "^3.0.0", "redux-thunk": "^0.1.0", "redux-undo": "^0.5.0" }, "devDependencies": { "babel-core": "^5.6.18", "babel-loader": "^5.1.4", "babel-plugin-react-transform": "^1.1.0", "babel-preset-es2015": "^6.3.13", "babel-preset-react": "^6.3.13", "babel-tape-runner": "^2.0.0", "enzyme": "^2.0.0-rc1", "expect": "^1.6.0", "express": "^4.13.3", "jsdom": "^7.2.2", "node-libs-browser": "^0.5.2", "react-addons-test-utils": "^0.14.6", "react-transform-hmr": "^1.0.0", "tape": "^4.4.0", "tape-run": "^2.1.2", "webpack": "^1.9.11", "webpack-dev-middleware": "^1.2.0", "webpack-hot-middleware": "^2.2.0" }} Here is the server.js:

I can't find any examples online of someone working with the normalizr tree in this way. The official example does no adding and removing so it was no help either.