News for hackers. Stuff that matters.

A comment on Scheduling in React. Parent comment

Re:Scheduling in React by bestest on Friday March 08, 2019 @03:51AM (#19336069)
That would happen when, for example, you're saving the value of the text input in redux, and the input is then updated with that value on change, although it's also updated by the user typing and the thread is blocked at the same time, thus we have a race condition.

That said — it only happens when one over-engineers stuff. Make sure to have a single source of truth, and that will be avoided.

[ Parent | on HN ]
Re:Scheduling in React by philipp-spiess on Friday March 08, 2019 @06:01AM (#19336567)
The best approach is to always updated the input synchronously in React (in the same tick when the event is handled). If you do it in another tick, you will always have to handle race conditions. This is a problem for all input elements though, not specific to React or even the Web.
[ Parent | on HN ]