3 ms·
Yes and by doing so you lost the advantages of a predictable and well organised API. GraphQL has first class support for this scenario.
by adamscybot 6y ago
Yes and by doing so you lost the advantages of a predictable and well organised API.
GraphQL has first class support for this scenario.
- systemvoltage 6y agoI disagree. You're shifting your "organization" to the frontend which becomes an utter cesspool of chaos. If anything changes in the backend, you will need to change the frontend as well. The whole point of an API is to decouple. GraphQL does the exact opposite.