Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

Proposal: error types #682

Closed
ehazlett opened this issue Mar 2, 2015 · 5 comments
Closed

Proposal: error types #682

ehazlett opened this issue Mar 2, 2015 · 5 comments

Comments

@ehazlett
Copy link
Contributor

ehazlett commented Mar 2, 2015

This would add support for error types instead of return fmt.Errorf everywhere.

Refs #553

@nathanleclaire
Copy link
Contributor

I think this is more of a "We need a coding style guide" than a specific issue which we can point at as definitively solved. I do agree strongly though.

@thaJeztah
Copy link
Member

@ehazlett @nathanleclaire not sure if this is the same thing, but you might be interested in the work @duglin and @stevvooe did here; distribution/distribution#548

@nathanleclaire
Copy link
Contributor

Nice callout @thaJeztah ; noted

@stevvooe
Copy link

stevvooe commented Jul 7, 2015

@thaJeztah The errcode package is targeted at API-level errors. We should start using it for any errors that may cross an http/rpc (and maybe cli) boundary.

@nathanleclaire @ehazlett We're still experimenting with the API, but Machine might want to explore use of the package.

@thaJeztah
Copy link
Member

@stevvooe yup, I was aware of that (API / http); I thought it might be interesting (for inspiration). Thanks for adding your thoughts 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants