codesandbox / codesandbox/codesandbox-client
Regarding enhancement of UX usability through auto saving and versioning of project with date
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
#🌈 Feature
it will be better if we could add auto saving and versioning of the files with time so that users can recover their files from given date
we can include one more item in files item in the navbar menu
user could pick a date to restore the file in modal window
since the files of the code are storing in local storage we can change it to globalstorage
and we can assign each saving module with minimum-gap of 1 day so that user can restore its code 1 day before , 2 day before , ... like this
i had came across this in my mind when i was using it to create my college website and i lost 1 day of hardwork by not saving the data
and in my opinion any user who came here to code from vs code get this problem because in vs code we have to ctrl+save each time any changes occur and here in code sandbox the situation is different it is easier , but it builds the habit of user to not save. So resulting user to get this type of mistake.
But autosaving the whole code to global storage and allowing user to restore its timely changed code can solve this usability probem.
I hope crux of the feature suggestion got conveyed.
issue
there is problem of renaming the large word length file if i hover to rename it just fades away
Contributor guide
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 Files item in the navbar and the existing local-storage handling, then trace how a restore modal could fit the current UI. Clarify the scope for dated autosave, version retention, restoration, and the separate long-filename rename issue; done requires an agreed design and acceptance criteria for both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100