Skip to content

refactor(NODE-5458): refactoring index operations to use async syntax #3774

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

Merged
merged 13 commits into from
Jul 27, 2023

Conversation

malikj2000
Copy link
Contributor

Description

index operations were converted from callback to async/await syntax

What is changing?

all operations in indexes.ts now use async syntax
DropIndexesOperation was removed, and Collection.dropIndexes now invoked dropIndex with a "*"

Is there new documentation needed for these changes?

No

What is the motivation for this change?

further converting the driver from callbacks to async/await

Release Highlight

Fill in title or leave empty for no highlight

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

@baileympearson baileympearson self-assigned this Jul 19, 2023
@baileympearson baileympearson added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label Jul 19, 2023
@baileympearson baileympearson marked this pull request as ready for review July 20, 2023 14:46
added metadata for failpoint in index_management
@baileympearson baileympearson merged commit ada1f75 into main Jul 27, 2023
@baileympearson baileympearson deleted the NODE-5458 branch July 27, 2023 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Primary Review In Review with primary reviewer, not yet ready for team's eyes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants