Fix: initialize IndexedDB with upgrade callback regardless of call order#83
Merged
shikokuchuo merged 4 commits intomainfrom Mar 26, 2026
Merged
Fix: initialize IndexedDB with upgrade callback regardless of call order#83shikokuchuo merged 4 commits intomainfrom
shikokuchuo merged 4 commits intomainfrom
Conversation
Collaborator
Author
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.
Fixes #82.
userSettings.tsopened the database without the upgrade callback that creates the stores. If it ran before projectStorage.ts (which it does on page load), the database was created empty and the stores were never created.This PR creates a single shared
getDb()in the storage module, used by both services.