cleaning out bad attempts

Open
#523 1 comment 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

The issue does not name any files, tests, or entry points. Start by locating where attempts are recorded and displayed, then determine how false starts or accidental inputs could be identified and evicted. Done should include an agreed triage behavior and coverage for the supported cases.

Written by the indexing model from the issue text.

Description

enhancement requires livesplit-core changes UI

Is there any way to triage the attempts so that we can evict ones that were broken? For example, false starts, or when the cat jumps on the splits key.

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.