Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
re #6922 there's a typo in
@5.2.16
,useCreateIndex
vscreateIndex
that causes any direct call to createIndexes ( barring the workaround below ) to always use the deprecated ensureIndexes method.As the variable name is internal only ( it gets added to options when using createIndex directly ) and only causes a deprecation warning, I didn't add any new tests for this change.
All current tests pass.
repo script:
indexExample.js
Output before change:
Output after change:
Temporary Workaround
You can pass an options object with
useCreateIndexes: true
as the first parameter toModel.createIndexes()
.like:
and circumvent the issue until the next release.