Feels like a schema design issue? If your REST backend exposes a single path to remove an item, are there any reason why your GraphQL schema doesn't expose a root mutation field taking the same arguments?

▲ fcpguru 2 days ago | parent [-]

yeah tell shopify, it's their api!

▲ johnjames4214 2 days ago | parent [-]

Exactly. If it's that verbose and painful for a public API like Shopify/GitHub (where the 'flexibility' argument is strongest), it makes even less sense for internal enterprise apps.

We are paying that same complexity tax you described, but without the benefit of needing to support thousands of unknown 3rd-party developers.

	▲	n_e 2 days ago \| parent [-]
		The issue is that the API itself is, I assume, badly designed. Equivalent delete queries in rest / graphql would be `curl -X DELETE 'https://api.example.com/users/123'` vs `curl 'https://api.example.com/graphql?query={ deleteUser(id: 123) { id } }'`