Open malhous opened 3 weeks ago
The conflict handler is not only used to handle conflicts but also to detect them. So it is called many times at various places. Next step would be that you create a PR with a test case to reproduce the problem. Maybe it is even reproducable without supabase which would make debugging easier.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. Please update it or it may be closed to keep our repository organized. The best way is to add some more information or make a pull request with a test case. Also you might get help in fixing it at the RxDB Community Chat If you know you will continue working on this, just write any message to the issue (like "ping") to remove the stale tag.
I am using RxDB along with a replication to Supabase. I have the following scenario:
Here's the code, i'm using React + Typescript:
For some reason
documents
are returned as[]
on the first observable emission, which is weird. But that's not my problem, what's then happening is that it's inserting the document into db, triggersconflictHandler
, which uses therealMasterState
but does not sync it with the local state.I'm not sure what are the next steps or how to solve it, any help would be great!
I'm using Dexie Storage and i noticed this empty function in
rxbd/src/plugins/storage-dexie/rx-storage-dexie-instance.ts
, not sure if it's relevant.