Disclaimer - I'm a massive GraphQL-fan and been building APIs and React-apps with (in production) since 2016. All the criticism below are specifically to do with Hasura and not GraphQL itself.
i have an app that has a type of product listings where something like "price" is optional
but price consists of several fields (amount, currency [and more that are irrelevant for this point])
so in the db they all have to be nullable, which is fine, but they are always presented as a group
typically, as a consumer you'd want a nullable price: Price
but i end up having to write custom client logic that I thought I was done with since starting making backends in graphql 4-5 years ago
getting started with having a nice dev environment that can be orchestrated easily with migrations etc in every env + locally + CI is a bit of a bitch
example, these two reqs are mutually exclusive
- I want role
userto access it's ownemail-field - I want role
userto access other users'name-field (but notemail)
"Inherit" rules of parent tables
I want to be able to use interfaces, unions, etc
Enforcing an api from db modelling becomes worse and worse with time and consistently causes breaking changes in your api.
One of the things that are amazing with GraphQL is the ease of non-breaking api changes and the built-in deprecation support combined with introspection. Hasura removes that.
1,100 open issues on github right now https://github.com/hasura/graphql-engine/issues
I've hit a bunch of them and when you do you have to do really awkward workarounds
actions are a good thought but then actually hooking it up to your backend and then orchestrating that in different environments (ci/dev/staging/prod) is horrible (although i've gotten continious deployment and automated e2e testing working it was a horrible process)
it's not nice to write sql functions to extend your schema