Feature/307 Clear local appdata on logout and fully reset discovery state#308
Open
chrislng wants to merge 5 commits into
Conversation
Prevents startup hangs and stale data failures caused by corrupted local data.
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
2 participants
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.
Clear corrupted/stale local DB files on logout and harden discovery UI and DB loading to prevent mount-time crashes and startup hangs caused by partial or invalid appdata/*.json. The logout flow now also clears in-memory DB caches, so stale discovery objects do not survive after logout/login.
This prevents the app from reusing stale in-memory state after logout/login and from loading corrupted local JSON produced by interrupted writes. It addresses the “patrimoine never loads” bug and reduces the chance of mount-time crashes in discovery modals.