Chris Waters

@skandragon You might want to try https://github.com/jwhitehorn/acts_as_versioned.

[Here is a jsfiddle](https://jsfiddle.net/x2pekbd4/25/) that demonstrates the desired behavior. ```javascript import { observable, observe } from 'https://unpkg.com/@nx-js/[email protected]/dist/es.es6.js'; const obj1 = { name: "My complex object", subObj: { val: 1 },...

I am trying to find standard patterns for our team to write React code. I am frustrated by the limitations in most React code with what actions can be performed...

I reproduced in repl.it here https://repl.it/@k1w1/WeepyBluevioletUsername using Chrome 81 on OSX. I observed the same problem in my application code which is babel transpiled. I see that the codesanbox.io example...

It looks like the difference is whether an async polyfill is being used. codesandbox.io is using a polyfill: repl.it is not using a polyfill: Where the polyfill is not being...

Plan B makes the most sense to me: If a reaction is triggered outside of a batch, then create a new batch that is scheduled to run the next time...

Your description above makes sense to me. From the debugging I have been doing in my real-world app I think it would solve the edge cases in a way that...

I am coming back to this issue. We are using react-easy-state quite extensively now. It is fantastic, but this batching problem still bites us. When it does happen it is...

My philosophy is that we cannot be paralyzed while waiting for Facebook to complete concurrent mode; we need to keep moving forward. My [PR](https://github.com/RisingStack/react-easy-state/pull/226) handles batching automatically, and completely without...

We are still using the code in the PR I linked above with great success. We use react-easy-state extensively and our team loves how quickly it allows us to write...