lordmauve / lordmauve/python-now
Save progress in localStorage
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Currently editor components are generated a unique ID that could act as a key to store their contents in localStorage.
We should be able to store changes before running code and load them whenever an editor is constructed.
This would require a "reset" button to revert the editor back to the content in the original markdown.
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 editor components and the code that generates their unique IDs, then inspect how editor construction receives the original markdown. Implementations should persist edits before execution, restore them when an editor is constructed, and provide a reset action that returns to the original markdown; verify each behavior in the browser.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100