Automatic Synchronization of Splits

Open
#994 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

The report mentions Chrome and lost splits and layout data but names no source files, tests, or entry points. Begin by reproducing the save and load failure in Chrome and tracing the existing persistence behavior; done should include confirmed synchronization or recovery without data loss.

Written by the indexing model from the issue text.

Description

enhancement needs further discussion / research support

Hello,
I've been using Livesplit One for 2-3 years. Recently I've been encountering issues of the page crashing, but a far more serious one has emerged. Recently, I was attempting to save both my splits and the layout earlier, but I got a message saying that it was not saved. Also the splits data would not load. I did not close the browser (Chrome) and hoped that the program would sort itself out, but the next time I came back to the page it had wiped away all my splits data. Is there any possibility of recovering anything here? Happy to provide more details on this issue.
I appreciate any help provided.

Dominant language
TypeScript
Stars
301
Forks
55
Avg merge
8m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LiveSplit/LiveSplitOne

All issues in LiveSplit/LiveSplitOne

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.