Order of writes, synchronizer, persister's load and save causing havoc

[haggen]

I'm building an app that should;

• Write to a participants table to signal a client has joined;
• Load from a persisted state in local storage;
• Start saving changes to the local storage;
• Synchronize with other connected clients;

But depending on the order I do these things I get all kinds of issues.

If I start persisting changes before loading the last saved state the whole store is overwritten. If I load first the participation is erased. All the permutations I tried I had issues. Which makes sense if I think about these problems, but shouldn't the CRDT nature of the store handle it?

I know these are hard problems but I thought the library would abstract it for me and let me deal just with my application. Am I doing something wrong?

Code: https://github.com/haggen/hindsight/blob/wip/src/components/Provider/index.tsx

[jamesgpearce]

Yep, this shouldn't be easy to get wrong! Let me look at your code to check.

BTW I don't seem to get notifications for 'discussions' vs 'issues' which it why I missed this at first, sorry!

[haggen]

Hey thanks for the reply!

If you wonder why I might have made this harder than it should with the weird useAsyncHook call and whatnot, on branch master I have a previous implementation with regular hooks: https://github.com/haggen/hindsight/blob/master/src/components/Provider/index.tsx

I changed it in an attempt to figure things out but better controlling the exact order things happen.