monkeytypegame / monkeytypegame/monkeytype

Custom Test To Zen Imcomplete Test Problem

Open
#8,170 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
20.7k
Forks
3.3k
PR merge metrics
No merged PRs in 30d

Description

Did you clear cache before opening an issue?
  • I have cleared my cache
Is there an existing issue for this?
  • I have searched the existing open and closed issues
Does the issue happen when logged in?

Yes

Does the issue happen when logged out?

No

Does the issue happen in incognito mode when logged in?

Yes

Does the issue happen in incognito mode when logged out?

No

Account name

RandomTyper128

Account config

No response

Current Behavior

So what basically happened is i did a custom test and didnt complete it and then i switched to zen and it didnt give me the incomplete xp but the test was long enough to be vaild but i also tried to go to the normal time/words mode and i didnt get incomplete XP

Expected Behavior

No response

Steps To Reproduce
  1. Create a custom test but dont complete it
  2. Go to zen and make it long enough to be vaild
  3. Notice the problem where you get no incomplete xp
  4. Switch To timer/words or quote and you get no incomplete XP
Environment
  • OS: Chrome OS
  • Browser: Chrome
  • Browser Version: Version 149.0.7827.153 (Official Build) (64-bit)
Anything else?

No response

Contributor guide

Open the contributing guide

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.

Research direction

No file, test, or code entry point is named. First reproduce the reported flow in Chrome while logged in, comparing an incomplete custom test followed by Zen, timer, words, or quote modes. The expected incomplete-XP behavior is not stated, so confirm the intended outcome before defining the fix and its tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.