Skip to content

Improve API error classification #36

@nicoweidner

Description

@nicoweidner

As observed in #35, the current error classification could use improvement. All 409 errors are described as ResourceAlreadyExists, which is not precise (see linked issue for an example).

I wonder why other error codes don't appear here either (e.g. 403, 415, ...)

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