Remove async void Dispose() anti-pattern from KvExplorerDb #137
+2
−8
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.
The
KvExplorerDbclass implementedIDisposablewith anasync void Dispose()method that created a new database connection just to close it—both an anti-pattern and unnecessary.Changes
IDisposableinterface fromKvExplorerDbasync void Dispose()methodusingstatement inKeyVaultTreeListViewModelconstructor for the singleton DI instanceRationale
Each method in
KvExplorerDbcreates and disposes its ownSqliteConnectionviausingstatements:No instance-level resource management is needed. The class is registered as a singleton, making disposal at the instance level inappropriate.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.