Closed coreGreenberet closed 2 years ago
Let's hold on this until dust settles on server-side fixes.
We can expect application/json content types for endpoints that return JSON content; this excepts any endpoint responding with a 204 No Content.
Given this, would you want to modify your PR in any way?
I think we should keep the PR like it is for 3 reasons:
1) The behaviour is then same as the request based version 2) There is no need for additional checks like 204 as the .json() method will handle that 3) If the backend creates a similiar issue again, we won't have troubles in the library
workaround for #177