4 ms·
tbh that doesn't sound like a Redux-specific problem. That sounds like a general async / stale-references problem. If you've captured a value and try to use i
by acemarke 7y ago
tbh that doesn't sound like a Redux-specific problem. That sounds like a general async / stale-references problem. If you've captured a value and try to use it later, then yeah, you're probably going not going to be using the latest version.
- mosdl 7y agoWhich is a design flaw of redux. Proper systems allow you to access the current state value at all times, without having to worry about batching.