Skip to content

Requests that fail aren't propagating errors  #74

@bolivier

Description

@bolivier

I was working with a subscription and the response came back with an error. Nothing checked for the error, so when a value was nil that shouldn't have been, my call returned a runtime error. That was difficult to track down. Perhaps this isn't different enough from #8 to warrant a new issue, but it's related. This is the line that is liberally catching the errors.

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