Do you have any plans to handle schema changes for the content stored within the CRDTs as the clients evolve?
(I've been puzzling over that question during some local-first dabbling; I have a feeling that lenses[1] -- or something like them -- may provide a route towards schema version upgrades without any peer synchronization guarantees)
(I've been puzzling over that question during some local-first dabbling; I have a feeling that lenses[1] -- or something like them -- may provide a route towards schema version upgrades without any peer synchronization guarantees)
[1] - https://www.cis.upenn.edu/~bcpierce/papers/lenses-etapsslide...