LiveSplit / LiveSplit/LiveSplitOne
Saving current splits on window reload
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 301
- Forks
- 55
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
Context: I'm using livesplit one to keep track of a long running challenge (I try to solve 400 puzzles that last between a few minutes to an hour each) which works well except for when I close the window, everything is wiped when I reload. Sadly this is a managed computer that requires restarting Chrome fairly frequently and I lose all the current splits.
Proposal: Would it be possible to periodically (every couple of seconds while the timer is running) save the current splits to localstorage and when you load the page, then use localstorage data.
I'm happy to do the implementation as well if someone is able to tell me how to serialize/deserialize the state of livesplit-core.
Thanks!
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 at the timer-running and page-load entry points, then determine how livesplit-core state can be serialized and deserialized for localStorage. Done means current splits survive a window reload and are restored when the page loads, without losing the active timer state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript, wasm
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100