Sorry Jack, but I tend to disagree. It doesn't worth the pain, IMHO. The client side has to hussle with the complexity of the backend. If you have Android ,ios, and react, you tripple the burden. BTW, something I learned recently, you can't use mutation and query at the same request.
Seasoned .NET Developer who is in love with Functional Programming, Serverless, Event-Driven Architectures, and Graph Databases. Former Microsoft FTE. Now, a contractor working in Ireland from Brazil.
Hey Uriel, can you give a concrete example of this?
To be fair, I agree that the toolling for graphql is indeed immature in many aspects (troubleshooting requests for example). But the main idea of asking the backend for only what you need is very interesting to be ignored, even on mobile.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Sorry Jack, but I tend to disagree. It doesn't worth the pain, IMHO. The client side has to hussle with the complexity of the backend. If you have Android ,ios, and react, you tripple the burden. BTW, something I learned recently, you can't use mutation and query at the same request.
Hey Uriel, can you give a concrete example of this?
To be fair, I agree that the toolling for graphql is indeed immature in many aspects (troubleshooting requests for example). But the main idea of asking the backend for only what you need is very interesting to be ignored, even on mobile.