Repository navigation
Implement custom errors #859
Description
Related to #857 (comment)
It would be nice to have custom error types in certain places to improve the error messages we provide to the user - instructing the user to access non standard properties to get the full error message seems painful, IMO errors should be obvious and in the users face.
Activity
stephenplusplus commentedon Sep 11, 2015
That's a wrapped error. We don't know what the underlying error is, so instead of giving them something potentially cryptic, we wrap it to at least let the user know what failed. How could a custom error type solve that?
callmehiphop commentedon Sep 11, 2015
I think if the error name was descriptive enough then the user should be able to deduce what happened without having to access additional properties for more info.
e.g.
SigningError: Cryptic error messagevs.
stephenplusplus commentedon Sep 11, 2015
I'd have to say, that makes a lot of sense!
fix(deps): use google-gax v3.5.2 (#859)
chore: remove snippet leading whitespace (#859)
feat(defaults): update defaults for the node client library to match …
feat(defaults): update defaults for the node client library to match …