You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in v4.x, the beforeSend callback receives a report object that does not include the original exception objects that are associated w/ the report. Having the original error instance included in the report would allow clients to leverage more sophisticated logic when determining whether or not to send the report along to the server. This would enable ember applications to leverage things like isAjaxError.
+1 on this. Specifically, it's not uncommon for 3rd-party libraries to put essential information about errors in ad-hoc properties. Some specific examples I've run into include:
@sendgrid/client: error.response.body.errors for errors returned from their service API
sequelize: error.original.sql for the raw SQL query, error.errors for data validation errors
joi: error.annotate() for validation error details
ajv: error.errors for validation error details
Being able to append this information to a bug report would be extremely helpful.
Desired Behavior & Use Case
Currently in
v4.x
, thebeforeSend
callback receives a report object that does not include the original exception objects that are associated w/ the report. Having the original error instance included in the report would allow clients to leverage more sophisticated logic when determining whether or not to send the report along to the server. This would enable ember applications to leverage things likeisAjaxError
.Related to #43.
The text was updated successfully, but these errors were encountered: