Skip to content

Surface API errors instead of discarding them #275

@digitalghost-dev

Description

@digitalghost-dev

Several flag functions discard the error from connections.*ApiCall via the _, _, _ pattern.

On a 404 or API failure the next field access nil-pointer panics instead of showing the styled "X not found" error. Capture and propagate the error since connections.FetchEndpoint already styles it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug/fixSomething isn't working or needs updating.

    Projects

    Status

    Completed

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions