— So the manager adds actions to a queue and executes them asynchronously, updating a temporary state object. Once all the actions are done and the queue is empty, THEN state gets updated :3
Also! to solve the problem of different actions having different state, I made it so they don't GET the actual state, but rather the PENDING state of the current queue!
— So per-cycle of executed actions, they all act on the same mutable, pending state
— Floofies you are solving a problem that you dont need to have
— Two actions cannot fire at the same
— If you are mutating the state based on the previous state, read the state with each event that mutates it
— React does that, look for the setState docs
— I am not using react
— I am building a Flux framework
— And I am not solving a grandiose problem, I'm enabling synchronous batched action scripting
— That allows me to invoke as many actions as I want, all at the same time.
— Here it is: http://pastebin.com/mc3dFqj9