fix: Slow and Steady Challenge Authentication (@AnnaBuchholz) by AnnaBuchholz · Pull Request #6319 · monkeytypegame/monkeytype

AnnaBuchholz · 2025-02-27T20:17:39Z

Description

I changed the Slow and Steady authentication to check if "liveSpeedStyle" is "off" rather than checking the if the legacy "showLiveWpm" was "false". This allows people to actually get the Slow and Steady challenge role automatically instead of getting a failure error even when they had liveSpeedStyle off.

Checks

Make sure the PR title follows the Conventional Commits standard. (https://www.conventionalcommits.org for more info)
Make sure to include your GitHub username prefixed with @ inside parentheses at the end of the PR title.

Closes #

…re already in this file and the British English spellings were already in the britishenglish file)

…d the American spelling was already in this file as well.

…as already in this file and in the britishenglish file)

…if the 25k already had the common American spelling

AnnaBuchholz · 2025-02-27T20:18:54Z

I think I just needed to update the legacy naming to fix the challenge authentication, but if I missed other places I need to change, please let me know.

fehmer · 2025-02-28T09:21:02Z

can you verify the fix is working locally?

AnnaBuchholz · 2025-02-28T17:43:50Z

I just tried doing the Slow and Steady challenge on localhost, but at the end there were no notifications at all (of challenge success or failure). It seems like I might need to be logged in to test the challenge authentication but I'm not sure how to log in as a user to test the challenge on the test site. Any idea what I could do to test it?

AnnaBuchholz · 2025-03-02T00:45:57Z

Alright, I posted some proof in the Discord. If there's anything else I need to do, please let me know.

Miodec

Thanks

AnnaBuchholz · 2025-02-27T20:17:39Z

Description

I changed the Slow and Steady authentication to check if "liveSpeedStyle" is "off" rather than checking the if the legacy "showLiveWpm" was "false". This allows people to actually get the Slow and Steady challenge role automatically instead of getting a failure error even when they had liveSpeedStyle off.

Checks

Make sure the PR title follows the Conventional Commits standard. (https://www.conventionalcommits.org for more info)
Make sure to include your GitHub username prefixed with @ inside parentheses at the end of the PR title.

Closes #

…re already in this file and the British English spellings were already in the britishenglish file)

…d the American spelling was already in this file as well.

…as already in this file and in the britishenglish file)

…if the 25k already had the common American spelling

AnnaBuchholz · 2025-02-27T20:18:54Z

I think I just needed to update the legacy naming to fix the challenge authentication, but if I missed other places I need to change, please let me know.

fehmer · 2025-02-28T09:21:02Z

can you verify the fix is working locally?

AnnaBuchholz · 2025-02-28T17:43:50Z

I just tried doing the Slow and Steady challenge on localhost, but at the end there were no notifications at all (of challenge success or failure). It seems like I might need to be logged in to test the challenge authentication but I'm not sure how to log in as a user to test the challenge on the test site. Any idea what I could do to test it?

AnnaBuchholz · 2025-03-02T00:45:57Z

Alright, I posted some proof in the Discord. If there's anything else I need to do, please let me know.

Miodec

Thanks

AnnaBuchholz · 2025-02-27T20:17:39Z

Description

I changed the Slow and Steady authentication to check if "liveSpeedStyle" is "off" rather than checking the if the legacy "showLiveWpm" was "false". This allows people to actually get the Slow and Steady challenge role automatically instead of getting a failure error even when they had liveSpeedStyle off.

Checks

Make sure the PR title follows the Conventional Commits standard. (https://www.conventionalcommits.org for more info)
Make sure to include your GitHub username prefixed with @ inside parentheses at the end of the PR title.

Closes #

…re already in this file and the British English spellings were already in the britishenglish file)

…d the American spelling was already in this file as well.

…as already in this file and in the britishenglish file)

…if the 25k already had the common American spelling

AnnaBuchholz · 2025-02-27T20:18:54Z

I think I just needed to update the legacy naming to fix the challenge authentication, but if I missed other places I need to change, please let me know.

fehmer · 2025-02-28T09:21:02Z

can you verify the fix is working locally?

AnnaBuchholz · 2025-02-28T17:43:50Z

I just tried doing the Slow and Steady challenge on localhost, but at the end there were no notifications at all (of challenge success or failure). It seems like I might need to be logged in to test the challenge authentication but I'm not sure how to log in as a user to test the challenge on the test site. Any idea what I could do to test it?

AnnaBuchholz · 2025-03-02T00:45:57Z

Alright, I posted some proof in the Discord. If there's anything else I need to do, please let me know.

Miodec

Thanks

AnnaBuchholz · 2025-02-27T20:17:39Z

Description

I changed the Slow and Steady authentication to check if "liveSpeedStyle" is "off" rather than checking the if the legacy "showLiveWpm" was "false". This allows people to actually get the Slow and Steady challenge role automatically instead of getting a failure error even when they had liveSpeedStyle off.

Checks

Make sure the PR title follows the Conventional Commits standard. (https://www.conventionalcommits.org for more info)
Make sure to include your GitHub username prefixed with @ inside parentheses at the end of the PR title.

Closes #

…re already in this file and the British English spellings were already in the britishenglish file)

…d the American spelling was already in this file as well.

…as already in this file and in the britishenglish file)

…if the 25k already had the common American spelling

AnnaBuchholz · 2025-02-27T20:18:54Z

I think I just needed to update the legacy naming to fix the challenge authentication, but if I missed other places I need to change, please let me know.

fehmer · 2025-02-28T09:21:02Z

can you verify the fix is working locally?

AnnaBuchholz · 2025-02-28T17:43:50Z

I just tried doing the Slow and Steady challenge on localhost, but at the end there were no notifications at all (of challenge success or failure). It seems like I might need to be logged in to test the challenge authentication but I'm not sure how to log in as a user to test the challenge on the test site. Any idea what I could do to test it?

AnnaBuchholz · 2025-03-02T00:45:57Z

Alright, I posted some proof in the Discord. If there's anything else I need to do, please let me know.

Miodec

Thanks

AnnaBuchholz · 2025-02-27T20:17:39Z

Description

I changed the Slow and Steady authentication to check if "liveSpeedStyle" is "off" rather than checking the if the legacy "showLiveWpm" was "false". This allows people to actually get the Slow and Steady challenge role automatically instead of getting a failure error even when they had liveSpeedStyle off.

Checks

Make sure the PR title follows the Conventional Commits standard. (https://www.conventionalcommits.org for more info)
Make sure to include your GitHub username prefixed with @ inside parentheses at the end of the PR title.

Closes #

…re already in this file and the British English spellings were already in the britishenglish file)

…d the American spelling was already in this file as well.

…as already in this file and in the britishenglish file)

…if the 25k already had the common American spelling

AnnaBuchholz · 2025-02-27T20:18:54Z

I think I just needed to update the legacy naming to fix the challenge authentication, but if I missed other places I need to change, please let me know.

fehmer · 2025-02-28T09:21:02Z

can you verify the fix is working locally?

AnnaBuchholz · 2025-02-28T17:43:50Z

I just tried doing the Slow and Steady challenge on localhost, but at the end there were no notifications at all (of challenge success or failure). It seems like I might need to be logged in to test the challenge authentication but I'm not sure how to log in as a user to test the challenge on the test site. Any idea what I could do to test it?

AnnaBuchholz · 2025-03-02T00:45:57Z

Alright, I posted some proof in the Discord. If there's anything else I need to do, please let me know.

Miodec

Thanks

AnnaBuchholz · 2025-02-27T20:17:39Z

Description

I changed the Slow and Steady authentication to check if "liveSpeedStyle" is "off" rather than checking the if the legacy "showLiveWpm" was "false". This allows people to actually get the Slow and Steady challenge role automatically instead of getting a failure error even when they had liveSpeedStyle off.

Checks

Make sure the PR title follows the Conventional Commits standard. (https://www.conventionalcommits.org for more info)
Make sure to include your GitHub username prefixed with @ inside parentheses at the end of the PR title.

Closes #

…re already in this file and the British English spellings were already in the britishenglish file)

…d the American spelling was already in this file as well.

…as already in this file and in the britishenglish file)

…if the 25k already had the common American spelling

AnnaBuchholz · 2025-02-27T20:18:54Z

I think I just needed to update the legacy naming to fix the challenge authentication, but if I missed other places I need to change, please let me know.

fehmer · 2025-02-28T09:21:02Z

can you verify the fix is working locally?

AnnaBuchholz · 2025-02-28T17:43:50Z

I just tried doing the Slow and Steady challenge on localhost, but at the end there were no notifications at all (of challenge success or failure). It seems like I might need to be logged in to test the challenge authentication but I'm not sure how to log in as a user to test the challenge on the test site. Any idea what I could do to test it?

AnnaBuchholz · 2025-03-02T00:45:57Z

Alright, I posted some proof in the Discord. If there's anything else I need to do, please let me know.

Miodec

Thanks

AnnaBuchholz · 2025-02-27T20:17:39Z

Description

I changed the Slow and Steady authentication to check if "liveSpeedStyle" is "off" rather than checking the if the legacy "showLiveWpm" was "false". This allows people to actually get the Slow and Steady challenge role automatically instead of getting a failure error even when they had liveSpeedStyle off.

Checks

Make sure the PR title follows the Conventional Commits standard. (https://www.conventionalcommits.org for more info)
Make sure to include your GitHub username prefixed with @ inside parentheses at the end of the PR title.

Closes #

…re already in this file and the British English spellings were already in the britishenglish file)

…d the American spelling was already in this file as well.

…as already in this file and in the britishenglish file)

…if the 25k already had the common American spelling

AnnaBuchholz · 2025-02-27T20:18:54Z

I think I just needed to update the legacy naming to fix the challenge authentication, but if I missed other places I need to change, please let me know.

fehmer · 2025-02-28T09:21:02Z

can you verify the fix is working locally?

AnnaBuchholz · 2025-02-28T17:43:50Z

I just tried doing the Slow and Steady challenge on localhost, but at the end there were no notifications at all (of challenge success or failure). It seems like I might need to be logged in to test the challenge authentication but I'm not sure how to log in as a user to test the challenge on the test site. Any idea what I could do to test it?

AnnaBuchholz · 2025-03-02T00:45:57Z

Alright, I posted some proof in the Discord. If there's anything else I need to do, please let me know.

Miodec

Thanks

AnnaBuchholz · 2025-02-27T20:17:39Z

Description

I changed the Slow and Steady authentication to check if "liveSpeedStyle" is "off" rather than checking the if the legacy "showLiveWpm" was "false". This allows people to actually get the Slow and Steady challenge role automatically instead of getting a failure error even when they had liveSpeedStyle off.

Checks

Make sure the PR title follows the Conventional Commits standard. (https://www.conventionalcommits.org for more info)
Make sure to include your GitHub username prefixed with @ inside parentheses at the end of the PR title.

Closes #

…re already in this file and the British English spellings were already in the britishenglish file)

…d the American spelling was already in this file as well.

…as already in this file and in the britishenglish file)

…if the 25k already had the common American spelling

AnnaBuchholz · 2025-02-27T20:18:54Z

I think I just needed to update the legacy naming to fix the challenge authentication, but if I missed other places I need to change, please let me know.

fehmer · 2025-02-28T09:21:02Z

can you verify the fix is working locally?

AnnaBuchholz · 2025-02-28T17:43:50Z

I just tried doing the Slow and Steady challenge on localhost, but at the end there were no notifications at all (of challenge success or failure). It seems like I might need to be logged in to test the challenge authentication but I'm not sure how to log in as a user to test the challenge on the test site. Any idea what I could do to test it?

AnnaBuchholz · 2025-03-02T00:45:57Z

Alright, I posted some proof in the Discord. If there's anything else I need to do, please let me know.

Miodec

Thanks

AnnaBuchholzand others added 18 commits January 6, 2025 16:27

Remove British spelling
036afe9

Remove derogatory word
2f40c43

Removed duplicate
0d782a6

Removed three (3) more duplicate words
4b24da7

Merge branch 'monkeytypegame:master' into master
e93359a

Fix: Deleted some British English words (the American English ones we…
8ea6435
…re already in this file and the British English spellings were already in the britishenglish file)

Fix: Removed British English word (already in british english file an…
890d0e3
…d the American spelling was already in this file as well.

Fix: Remove British English spelling (the American English spelling w…
0a15032
…as already in this file and in the britishenglish file)

Merge branch 'monkeytypegame:master' into master
f18d6c7

Merge branch 'monkeytypegame:master' into master
7fb4edb

Fix: Moved some words to britishenglish file (and deleted duplicates …
ea8ff4f
…if the 25k already had the common American spelling

Fix: Removed some potentially questionable words
3c007a7

Removed duplicate word
10d1a97

Fixed mispelling
05fff69

Fix: moved British English spelling to britishenglish file
941577e

Merge branch 'monkeytypegame:master' into master
4a09efc

Merge branch 'monkeytypegame:master' into master
1fd77c8

fix: Updated legacy live wpm to current name
012feec

monkeytypegeorge added frontend User interface or web stuff assets Languages, themes, layouts, etc. labels Feb 27, 2025

Miodec approved these changes Mar 3, 2025
View reviewed changes

Miodec merged commit 12ab49c into monkeytypegame:masterMar 3, 2025