-
It's an easy mistake to make. Currently Replicache logs if the cookies goes *down* but it doesn't log if it stays equal.
-
Replicache UIs are currently built using the [`subscribe()`](https://doc.replicache.dev/api/classes/Replicache#subscribe) method.
The idea of subscribe is that it is an arbitrary function of a Replic…
-
Right now it is possible to use Replicache with Solid, but not easy since there are no samples and not efficient since Replicache's `subscribe()` method returns the entire dataset each time it runs de…
-
Currently it is difficult to use the `drop` API correctly in Replicache. Users must ensure that all connections to the same named replicache instance (across all tabs!) first close their connections. …
-
At the moment for v0.1.0 we will load (pull) data from Gauzy APIs periodically (e.g. every 0.5 sec) to update Team page and other details.
For v0.2.0 we want to implement more real-time updates (th…
-
Currently transaction arguments are decoded in both repc and replicache-sdk-js in various locations. This is both expensive and also prevents us from easily doing useful sanity checks.
-
Undo/redo is a very common feature request in collaborative applications and doing it correctly is somewhat subtle (e.g., see posts by [Figma](https://www.figma.com/blog/how-figmas-multiplayer-technol…
-
Right now if most Replicache callback interfaces throw, we catch the error and put it to console.
The rationale is that user code is not typically below us in the stack so if we throw, it's going t…
-
I am building real-time collaboration tool.. what's the best to subscribe for changes in model on frontend?
-
The current protocol does not support deleting old client records. This is because clients are created implicitly by either push or pull, and the clientID is user-supplied.
So if a client record is…