-
Notifications
You must be signed in to change notification settings - Fork 493
Thoughts on using github.com/pkg/errors for errors #189
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
Comments
I think adding a stacktrace is a good idea. I believe the preference for this library is to keep external dependencies minimal. Maybe there exists a way to get the stacktraces without adding the dependency? What do you think about that? |
The |
Yes I would consider that an option 👍 |
Shameless plug: you can switch it to drop-in replacement |
I'm closing this issue as it doesn't currently solve some issue with this library. |
I'd like to propose the idea of using
github.com/pkg/errors
for errors.Logging regular errors and panic errors could give us proper stack traces which makes debugging / fixing problems much easier because you can see from where the error has been returned.
I have already applied this on our fork (see https://travis-ci.org/qdentity/graphql-go) and all tests pass.
I'm happy to create a PR if this idea is also useful for this repo.
The text was updated successfully, but these errors were encountered: