Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Implement client-specific error structures #5

Closed
ionut-arm opened this issue Mar 20, 2020 · 1 comment · Fixed by #8
Closed

Implement client-specific error structures #5

ionut-arm opened this issue Mar 20, 2020 · 1 comment · Fixed by #8
Labels
enhancement New feature or request

Comments

@ionut-arm
Copy link
Member

The initial client returns raw ResponseStatuses as error values for all its methods. A better solution would be to return a client-specific error type which would make a distinction between errors originating in the service and errors raised by the client itself.

This should be done before #4

@ionut-arm ionut-arm added the enhancement New feature or request label Mar 20, 2020
@ionut-arm
Copy link
Member Author

The conversions happening implicitly within the RequestHandler should be modified to point to errors belonging to the client, not to the service

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant