fix: include options parameter in createIndex method #794
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.
Problem: When defining custom index names in model settings, the connector was ignoring the specified
name
option and falling back to MongoDB's default naming convention (e.g., "archived_1" instead of "archived").Root Cause: The
createIndex()
call was missing theoptions
parameter, so custom index options including thename
field were not being passed to MongoDB.Solution: Updated the
createIndex()
call to include theindex.options
parameter:Checklist
npm test
passes on your machine (fails 1 test but this is unrelated)