Continuing my explorations of RxDB and Rescript, this article hooks up mutations to allow RxDB to automatically sync its offline-enabled changes to the graphql server.
I’ve become quite comfortable in Rescript over the course of the past few months. So far in this long-running series, I’ve implemented an RxDB powered offline-enabled application in Rescript. I’ve also written a graphql server using express. In this article, we’ll connect the two so that the RxDB frontend can sync with the graphql database.
In the previous article we implemented the sync read endpoints between our graphql server and our RXDB client. In this one, we’ll hook up the mutations.
Now that our Rescript client and server have the same data model, we can hook up the graphql endpoints to sync the offline rxdb database with the graphql server.
Continuing my ongoing series on the Rescript programming language, I discovered I needed to refactor my backend to better suit the graphql queries the frontend has to make to it.
Rescript is a delightful programming language pulling in the best elements of Javascript and functional languages without the worst bits of either. In this article, we create a graphql server in Rescript.
Instead of writing a new article on Rescript this weekend, I ended up writing an entire project in Rescript!
rescript-zora provides Rescript bindings to the lightning-fast zora unit testing framework. I chose zora because it has excellent SEO for “fastest javascript test framework”, and it deserves it.
