Skip to content

Responses swallowed when there's an unmarshaling error #106

@KirkEasterson

Description

@KirkEasterson

Problem: If a response results in an error when being unmarshaled, the response is lost. This makes it impossible to differentiate a 200 response from a 400 response.

This code highlights the issue. If I receive an unmarshaling error, I don't know if the fault was mine or not.

Suggested fix: Wrap the err with content included, or use some structured error that contains more information about this issue.

I can work on this, but how to handle this case should be decided by more than just me.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions