Skip to content

fix(ux): user-facing error messages (#207, #211, #208)#224

Merged
dmccoystephenson merged 1 commit into
mainfrom
feature/user-facing-errors
Jun 14, 2026
Merged

fix(ux): user-facing error messages (#207, #211, #208)#224
dmccoystephenson merged 1 commit into
mainfrom
feature/user-facing-errors

Conversation

@dmccoystephenson

Copy link
Copy Markdown
Member

Summary

Replaces developer-facing error copy with plain language:

Test plan

  • npm run lint clean, npm run build succeeds.
  • Manual trace: each setError(...) path now shows the new copy; technical detail stays in console.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

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>
@dmccoystephenson

Copy link
Copy Markdown
Member Author

Self-review rubric (CI green):

@dmccoystephenson dmccoystephenson merged commit 9afbb06 into main Jun 14, 2026
2 checks passed
@dmccoystephenson dmccoystephenson deleted the feature/user-facing-errors branch June 14, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant