hyperfiddle-2020
hyperfiddle-2020 copied to clipboard
race condition in `with-entity-change-route!
If you beat the server, you can clobber the last entry
multi-pickers can easily reproduce this race condition in everyday happy-path usage Apparently this transaction confuses the server, why can we see :riverside ?
https://github.com/hyperfiddle/hyperfiddle/issues/637
Shouldn't requests
- be debounced at the HTTP client level
- wait for the response to come back before sending the next request
- only keep the last route change? (dropping buffer of size 1)