Skip to content

Conversation

@teg-atlassian
Copy link
Contributor

@teg-atlassian teg-atlassian commented Feb 9, 2026

What Is This Change?

Small bug fix to gurantee that null strings don't throw exceptions so that we can avoid errors.

How Has This Been Tested?

Basic checks:

  • npm run lint
  • npm run test

Advanced checks:

  • If Atlassian employee & Bitbucket changes: did you test with DC in mind? See Instructions

Recommendations:

  • Update the CHANGELOG if making a user facing change

Rovo Dev couldn't review this pull request
Upgrade to Rovo Dev Standard to continue using code review.


const hasRetryableErrorCode = retryableErrors.includes(errorCode);
const hasRetryableErrorInMessage = retryableErrors.some((code) => errorMessage.includes(code));
const hasRetryableErrorCode = retryableErrors?.includes(errorCode) ?? false;
Copy link
Collaborator

Choose a reason for hiding this comment

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

nitpick: in javascript undefined evaluates as false, so a fallback value to false here (and below) is not necessary

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.

2 participants