Skip to content

Handle common HTTP error responses #2

Description

@bombsimon

Right now we unconditionally tries to deserialize the response to a type such as Device or Scene. This doesn't work well when the request was failing for common reasons such as with HTTP 404 Not Found.

We should add a better way to look at the response code to determine a reasonable type for body deserialization.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions