Radek Pietruszewski

> So I can fork this repo and get it to work for my purposes. Ideally this change could make it's way into your repo, if it's something you want....

> Why you prefer client side ids instead backend No, we prefer client and backend IDs being equivalent, because it makes things a lot simpler. Explained here: https://github.com/Nozbe/WatermelonDB/blob/master/docs-master/Advanced/Sync.md#local-vs-remote-ids

Unfortunately not. Autoincrementing ids are hard to reconcile with synchronization. Why do you want to have incrementing int ids anyway?

@rozPierog can you review in a spare moment?

@rozPierog ⬆️

> 'm not sure if this is a feature that you're even interested in merging it is! I'm not promising when I'll take a closer look at this, but I...

> Have you checked if native/iosTest works correctly? It didn't used to use WatermelonDB via CocoaPods but via old-school linking, so I'm not sure if we can make the breaking...

@cjroth iosTest changes are merged to master, so when you merge in master here, CP-only is going to be fine. PS: If you can configure the PR so that I...

> Sorry still haven't had much time No rush! > @radex what do you mean exactly? Happy to do whatever helps you! This checkbox: https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork

@cjroth hey, are you planning to finish this in the near future? Conflicts are creating themselves :(