OpenCloning / OpenCloning/OpenCloning_frontend
Issue with localStorage versions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 10
- Avg merge
- 11d 9h
- Merged PRs (30d)
- 3
Description
Hello,
After upgrading to a new version, there was this warning in the console:
I believe the issue is that the app doesn't expect to find older versions of values stored in localStorage.
I suggest tracking the version of localStorage so you can detected if localStorage elements should be upgraded or at least cleaned up when the app starts.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the frontend code that reads and writes localStorage, then reproduce the warning after upgrading from an older app version. Determine which stored values are affected and document the expected migration or cleanup behavior; done means upgrades handle old values without the reported console warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100