Client: handle 409 HTTP code #132

lunny · 2018-12-04T22:02:01Z

lunny commented

2018-12-04 22:02:01 +00:00

This is helpful, as POST /api/v1/releases returns no HTTP body for a 409 request,
eg when there already is a release for the specified tag.

The underlying problem is bigger:
The Client cannot handle error responses which do not contain a valid JSON body.
I tried to solve it by still printing a usable error message instead of a JSON parsing error

Author: @noerw This is helpful, as `POST /api/v1/releases` returns no HTTP body for a 409 request, eg when there already is a release for the specified `tag`. The underlying problem is bigger: The Client cannot handle error responses which do not contain a valid JSON body. I tried to solve it by still printing a usable error message instead of a JSON parsing error

Sign in to join this conversation.

No reviewers

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/go-sdk#132