Why is Codemirror#componentWillReceiveProps async?

There might be a very good reason I’m not aware of for debouncing componentWillReceiveProps by default, but it created a lot of headache when it comes to state synchronization (refs https://github.com/mozilla-services/react-jsonschema-form/pull/175).

What’s the reasoning behind scheduling it to the next tick, perfs? Could it be conceivable to make this an optional behavior?

[sslotsky]

The debouncing causes me some trouble as well. It appears that the debounce applies to all instances of the component on a page simultaneously, so if they all try to re-render at once, only the last instance will actually show a change.

This was the issue I described in #46, which I closed because I found a way to work around it. However, this will still be a problem for instances like drag & drop sorting, where there is more than one instance that legitimately needs to re-render at the same time.

Here’s a link to a video demonstrating the issue.

https://youtu.be/-mbHy17bxZw

[scniro]

This appears to be a duplicate of #106. I ran into the same issue and created react-codemirror2 because I was dying over the debouncing issue (and couldn’t sleep at night with the lodash dependency). My wrapper component is very barebones, surely needs some more work, but works well for my simple usage. I’ll be maintaining it moving forward so any struggles going on here I’ll happily work out in the alternative package. Please let me know if anyone takes the time to check it out and finds it useful - thanks.