Live progress doesn't update after custom text change

Open
#8,334 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Reproduce this in custom mode using the commandline's “change custom text” flow, then trace how the new text length reaches the live progress display. Verify that after confirming asdf asdf, progress immediately shows 0/2 before any typing, and rerun the listed steps to confirm the default text length is no longer shown.

Written by the indexing model from the issue text.

Description

bug
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?

Yes

Does the issue happen in incognito mode when logged in?

Yes

Does the issue happen in incognito mode when logged out?

Yes

Account name

No response

Account config

No response

Current Behavior

After changing the custom text, the live progress doesn't update to the length of the new custom text (e.g., if text is my random text, it doesn't say 0/3) until you type the first word.

Expected Behavior

Live progress should update to the new length.

Steps To Reproduce
  1. Set mode to custom
  2. Open the commandline, type change custom text and press enter
  3. Set the custom text to asdf asdf
  4. Click on ok
  5. Type a
  6. Notice how the live progress says 0/9 (the length of the default text) instead of 0/2
Environment
  • OS: Arch Linux
  • Browser: Firefox
  • Browser Version: 153.0.3
Anything else?

No response

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

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.

More from monkeytypegame/monkeytype

All issues in monkeytypegame/monkeytype

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.