fix(ux): user-facing error messages (#207, #211, #208)#224
Merged
Conversation
Login/register/leaderboard failures no longer ask the visitor "Is the API running?", and a failed registration no longer guesses "username may already be taken" — it points at both the username and the password requirements. Closes #207 Closes #211 Closes #208 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Member
Author
|
Self-review rubric (CI green):
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces developer-facing error copy with plain language:
account.tsxlogin/register connection errors no longer say "Is the API running?".leaderboard.tsxload failure no longer says "Is the server running?".Test plan
npm run lintclean,npm run buildsucceeds.setError(...)path now shows the new copy; technical detail stays inconsole.error.Note: the profile/API-key handlers use a plainer "Connection error." — not developer-speak and outside the named issues, so left unchanged.
Closes #207
Closes #211
Closes #208