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
As a follow-up to #2569, it would be very helpful if each error in the cause chain was logged with all of their additional properties (rather than just the message, source, type and stack)
This would be very helpful for us in cases where we want to include additional debugging information in an error we are throwing in a deep context which is then embedded as a cause and reported to datadog. We have had to work around this by just including it in the error message for now. See: https://github.com/pixiebrix/pixiebrix-extension/pull/9262/files
Thank you for your feedbak and sorry for the delay. We are considering adding support for additional context through a dd_context property, so your usecase could look like this:
As a follow-up to #2569, it would be very helpful if each error in the cause chain was logged with all of their additional properties (rather than just the message, source, type and stack)
This would be very helpful for us in cases where we want to include additional debugging information in an error we are throwing in a deep context which is then embedded as a cause and reported to datadog. We have had to work around this by just including it in the error message for now. See: https://github.com/pixiebrix/pixiebrix-extension/pull/9262/files
For reference this was the change to support error causes:
https://github.com/DataDog/browser-sdk/pull/2602/files
The text was updated successfully, but these errors were encountered: