DISCUSSION: At what level of granularity should we have error classes matching API errors?

[dhermes]

See #177 for more details.

Error Docs:
https://cloud.google.com/storage/docs/reference-status

[jgeewax]

I think it might be worthwhile to group them by code and then store the other details under that umbrella.

A 400 (bad request) could be BadRequestError which has a description and a message (and ideally something explaining what you did wrong...). This way we can catch the high-level stuff... and then dig into detail about what exactly went wrong (and raise again if it's something we don't want to handle)

Just my $0.02.

[tseaver]

I believe this issue basically duplicatd #164, fixed via #355, which maps each HTTP response status to a separate exception class.

We can't really document all the exceptions we could be raising, because the upstream API docs don't specify which response status codes can be returned from individual APIs.