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

Support error cause #1012

Merged
merged 1 commit into from
Apr 7, 2022
Merged

Support error cause #1012

merged 1 commit into from
Apr 7, 2022

Conversation

waltjones
Copy link
Contributor

Description of the change

This PR adds support for the Error cause option enabled in Node 16.9, Chrome 93, and other browsers. (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/Error#browser_compatibility)

This PR leaves the existing Error.nested functionality for back compatibility with existing Rollbar.js usage and with earlier Node and browser versions. When Error.nested is present, it is preferred, preserving existing behavior.

Type of change

  • New feature (non-breaking change that adds functionality)

Related issues

Fixes #1010

Development

  • Lint rules pass locally
  • The code changed/added as part of this pull request has been covered with tests
  • All tests related to the changed code pass in development

Code review

  • This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
  • "Ready for review" label attached to the PR and reviewers assigned
  • Issue from task tracker has a link to this pull request
  • Changes have been reviewed by at least one other engineer

Copy link
Contributor

@ijsnow ijsnow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Nifty that its just a map of existing rollbar functionality.

if (chromeMajorVersion() < 93) return;

it('should create trace_chain', function(done) {
var causeErr = new Error('cause error');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know all old tests use the old var syntax but is there a reason to continue using them as opposed to const/let?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just consistency. I'd rather not have a mix until we're actually switching over to const/let.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for Error cause field
2 participants