Skip to content

Conversation

@baileympearson
Copy link
Contributor

Description

What is changing?

MongoErrors now appropriately handle AggregateErrors and construct a message from the error messages of each sub-error.

Is there new documentation needed for these changes?

No.

What is the motivation for this change?

Double check the following

  • Ran npm run check:lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket
@nbbeeken nbbeeken self-requested a review May 24, 2023 15:50
@nbbeeken nbbeeken self-assigned this May 24, 2023
@nbbeeken nbbeeken added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label May 24, 2023
@baileympearson baileympearson requested a review from nbbeeken May 24, 2023 17:55
@baileympearson baileympearson requested a review from nbbeeken May 24, 2023 20:30
@nbbeeken nbbeeken added Team Review Needs review from team and removed Primary Review In Review with primary reviewer, not yet ready for team's eyes labels May 24, 2023
@nbbeeken nbbeeken merged commit e03178e into main May 25, 2023
@nbbeeken nbbeeken deleted the NODE-5296-aggregate-error-5.x branch May 25, 2023 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Team Review Needs review from team

3 participants