Closed Eun closed 4 years ago
Will fix these tests asap.
Ready to merge
Can we just make execute
smart enough to treat all 2XX codes as successful so we don't have to pass http.StatusAccepted
to every call?
Accepting all 200 codes feels a bit risky, instead I would rather just add the specified 200 codes from spotify:
https://developer.spotify.com/documentation/web-api/#response-status-codes
Sure, but the reason we're in this situation is that Spotify sometimes sends 200 codes that it doesn't document, and thus this library issues an error when the operation succeeded..
I haven't seen 200 codes that are undocumented. I can extend execute
to treat 200, 201, 202 and 204 as success like they say here.
@Eun any follow up on extending execute
as mentioned above?
closes #99