Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Move towards using only named errors #131

Closed
whyrusleeping opened this issue Sep 28, 2014 · 1 comment
Closed

Move towards using only named errors #131

whyrusleeping opened this issue Sep 28, 2014 · 1 comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@whyrusleeping
Copy link
Member

It would be nice to move away from doing return errors.New("Blah Blah Blah") and start making global scope error variables. This will make it easier to handle certain errors we might be expecting and clean up the codebase a bit.

@whyrusleeping whyrusleeping added the kind/enhancement A net-new feature or improvement to an existing feature label Sep 28, 2014
@jbenet
Copy link
Member

jbenet commented Sep 29, 2014

+:100:

@jbenet jbenet closed this as completed Mar 28, 2015
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Feb 25, 2022
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Feb 25, 2022
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Mar 4, 2022
laurentsenta pushed a commit to laurentsenta/kubo that referenced this issue Mar 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants