Repository navigation
feat(database): add index management capability - #15
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR adds optional index management support to the database package by introducing a dedicated
IndexManagercapability and implementing it for both the MongoDB client and the mock database.The main motivation is to make index creation a first-class, reusable operation without coupling the database layer to application-specific schema or index definitions. Consumers retain ownership of their indexes, while the shared database client now exposes a consistent way to create and manage them.
This improves the project by:
MockDatabasewith full index creation support, including call tracking, queued responses, expectations, and reset handling.CreateManybehavior, making index setup safe to run repeatedly during startup or deployment workflows.The accompanying tests validate both successful index creation flows and error handling behavior to ensure the new capability behaves consistently in production and test environments.