fix: cross-entity React Query auto-invalidation for DB mode#15
Open
fix: cross-entity React Query auto-invalidation for DB mode#15
Conversation
…alog race condition - Remove async/await from better-sqlite3 transaction callbacks - Add .run() for mutations and .all() for queries in transactions - Wait for React Query cache refresh before closing add-game dialog - Add error handling to prevent dialog close on failure Fixes issue where better-sqlite3 v11.10+ throws "Transaction function cannot return a promise" error. Also fixes race condition where dialog would reopen immediately after adding a game due to stale cache. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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
1 participant
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.
Summary
useGameManagementActions,useSettingsActions,useProfileActions,useModManagementActions) now use a unifiedinvalidatehelper that is a no-op in Zustand mode and firesqueryClient.invalidateQueriesin DB modeaddManagedGame,removeManagedGame) now cascade-invalidate dependent queries: profiles, modManagement, and settingsensureDefaultProfile,createProfile,deleteProfile,resetGameProfilesToDefault,removeGameProfiles) now also invalidate the modManagement cacheTest plan
Fixes #13, fixes #14
🤖 Generated with Claude Code