why `apiResponseCode` and not `httpResponseCode`
loic425 opened this issue · comments
Not within scope of current PR and just thinking out load -- I find these exceptions strange, why apiResponseCode and not httpResponseCode or why it need this property at all, it doesn't feel like resource exception, but rather like some app-level exception.
Originally posted by @diimpp in #768 (comment)