Fix/1268 push error field

[maratal]

No description provided.

[lawrence-forooghian]

Perhaps before we start trying to parse this field, we should get it added to the documentation for the "get details from a registered device" etc REST API endpoints?

[lukasz-szyszkowski]

Perhaps before we start trying to parse this field, we should get it added to the documentation for the "get details from a registered device" etc REST API endpoints?

Isn't described in Common API behavior -> General? Just below the text All other standard HTTP statusCodes signify an error. Errors from all APIs are returned as an object of the form:

{
  error: {
    code: <ably error code>,
    message: <string>,
    statusCode: <http status code>
  }
}

🤔

[lawrence-forooghian]

No, I think that’s describing what the response looks like if there’s an error in responding to the HTTP request. The error we’re talking about here is nested inside an object that represents a device, and I believe may be present even if the response has a 200 status.

[lukasz-szyszkowski]

No, I think that’s describing what the response looks like if there’s an error in responding to the HTTP request. The error we’re talking about here is nested inside an object that represents a device, and I believe may be present even if the response has a 200 status.

agree 👍

[lawrence-forooghian]

@maratal looks like this isn't ready for review and there's been no activity on it for a while, so I've converted it to a draft.

[maratal]

Blocked by docs ably/specification#23 (comment)