How often do you wrap your errors?

[JOhn_Stuart (Les Way)]

When does it make snese to wrap an error with additional info ?

For example, GetObjectX() makes a REST call or a DB call, and that call returns and object and error. If that error is not nil, do oyu return it as is or wrap it with:

errors.Wrap(err, "Could not get an answer from API")

Please advice.

[connerj70 (Conner Jensen)]

@JOhn_Stuart

t make snese to wrap an error with additional info ?

For example, GetObjectX() makes a REST call or a DB call, and that call returns and object and error. If that error is not nil, do oyu return it as is or wrap it with:

Hey!

Where I work we pretty much wrap all of our errors with extra information. This makes it really nice when looking at errors and you can see the entire path to where the error originated from. That being said sometimes wrapping the very “bottom” error seems pointless if your function only has one place that returns an error.