More aggressively catch corrupted local storage #1031
Draft
+9
−1
Conversation
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
jason4193
requested changes
Jul 15, 2025
Contributor
jason4193
left a comment
jason4193
left a comment
There was a problem hiding this comment.
After running test locally, identify these errors.
useReftype error on utils- case of updated timetable not save on localStorage when
version > 2
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 🧾
Motivated by seeing our second user with corrupted storage, already migrated to version 2. Something is very wrong here - we should look at where new terms get created/added, as well as all of the code that syncs data from the user database to local storage. In the meantime/since we are replacing that code anyway, my fairly destructive check that gets users out of binds can be run once per refresh to try and get users out of this issue.
Testing
Not tested yet - I will have more time later this week.