Persistent browser memory of IDE changes
Problem to solve
When editing code within GitLab IDE, the changes are forgotten by the browser on next launch. It should be stored locally instead in localStorage or SQLite.
Target audience
Everyone, who edits code, templates or documentation within GitLab IDE.
Further details
- Change something in your IDE.
- Kill the browser
- Open it again
- The changes should appear again
Proposal
Use browser storage to store latest changes. There may be some kind of limit, to drop changes older than a month for example.
What does success look like, and how can we measure that?
- Change something in your IDE.
- Kill the browser
- Open it again
- The changes should appear again