-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Add new client error exception #745
Conversation
This does not change anything in the logs. Should the logging be changed to match the correct message response coming from client error module? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left A BUNCH of comments, sorry! Fantastic work though, this is exactly what I had in mind. 🙃
2d8a9dc
to
d06ff76
Compare
lib/sentry.ex
Outdated
@typedoc """ | ||
An error that is returned from Sentry Client. | ||
""" | ||
@type error :: ClientError.t() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m thinking we don't need to introduce this for now since ClientError
is public, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking preemptive in case we introduce more error types but removed this. You're right, it's redundant.
018ee5c
to
6aa7c97
Compare
Yeeehaaaw |
-add client error module to handle Sentry client errors