Closed jimthedev closed 4 years ago
It catches and prevents race conditions -- changes are applied optimistically in the frontend immediately, then re-sent once they are "finalized" in the backend. It might be possible to detect the no-op case and not emit the change again, but I've been using hypermerge with React which already takes care of that for me.
Hello. When using
repo.watch
, why are local changes are repeated?