Matthew Brimmer

@xDemon200 Did you happen to fork this package? I am not sure if this is being maintained anymore. Would love to use your fork if you were able to successfully...

Some minor changes were committed a week ago. I really hope they continue maintaining it. I love it so much more than Jotai tbh.

@zsnmwy What is the state of your fork? It doesn't look like this library is being maintained and might require significant work with the new `jsonProtocol`.

> @mbrimmer83 Now it supports `Prisma 5.0`, especially for `jsonProtocol`. More detail in repos. https://github.com/zsnmwy/prisma-data-proxy-windmill-template https://github.com/zsnmwy/prisma-data-proxy Oh wow, I'm gonna test it out this weekend. I'll let you know how...

The only thing I've read that would cause a pushed object not to marked as synced is if it changed during the sync and that hasn't happened in this case....

Ok, so I wrapped my entire sync function in a try catch and get an error inside watermelon `TypeError: Cannot read property 'type' of undefined` Top of stack inside _setRaw....

> Did you manage to solve this? > > Didn't go into detail but there is explicit check for [updatedAt](https://github.com/Nozbe/WatermelonDB/blob/62774d5ebc4aa9ed6a2f61c8d4e795b32322cec6/src/Model/index.js#L130). I don't think these fields are mandatory but if defined...

Overall I don't like that Watermelon uses naming conventions like this. In my opinion you should be able to configure the columns you want to attach advanced field behaviors to....

I don't have any bandwidth to work on this, but pledged $100 to help support this work. Would love this feature.

I'm curious about this as well and I don't think this is going to work with the new `jsonProtocol`. Might require a complete rewrite. but I'm not sure this library...