We're using neo4j-graphql-js. It's absolutly incredible tool. Managing a database and API thru a simple Schema is amazing approach. Thank you so much for that. We're huge fan.
I'm trying to figurate how to do a simple mutation which involve 2 mutations. Let me explain:
When I do CreateMyType() mutation, it's always followed by a mutation addMyType1ParentType() to link the created node to a related node. This example is show the most simple case but often, there's more than 2 mutations (as there's many link and node creation related to the creation of one node) which needs to be done in one requests from the front end.
I'm wondering how you plan to make such mutations easier. I've to plan with my dev team the best approach to do that.
Would it be to write custom resolvers which will be in charge to receive one "call" from the frontend, and then, do the few mutations with existing mutations created by neo4j-graphql-js, and respond to the frontend whatever is needed ?
Or what would you suggest?
Also, in the background of this question, there's the notion of transaction. If one mutation fail, all should fail.
This demand is quite urgent for us.
Thank you so much