3 ms·

Request failed successfully

• locknitpicker 4mo ago
  It's the graphql way.
• gbuk2013 4mo ago
  Not really, more like succeed without having to do anything. The key is the perspective of what success is: it’s the state where the resource does not exist, or is the action having deleted the resource. But 200/202 is perfectly capable of expressing the distinction in the latter case as well.