The sync part is very interesting, I like that it’s happening after the mutation so that Im not forced to reimplement the graphql types myself.
Will give it a try, thanks
Will give it a try, thanks
What I really want/need is custom logic that run IN the resolvers of already available query/mutations with the request as input and the possibility to either return an error or modify the payload before it hit the database
but I know is still in preview, will check it again when released