Skip to content

UX Improvement: Display a user-friendly message for GitHub API rate limit errors instead of raw JSON #72

Closed

Description

@GowsiSM

When a user hits GitHub's secondary rate limit, the application displays a raw JSON error directly on the page. This is a poor user experience and can confuse or frustrate users who don't understand API rate limiting.

Current Behavior
The error is shown as raw text, like this:

Search failed
GitHub API error 403: { "documentation_url": "...", "message": "You have exceeded a secondary rate limit. Please wait a few minutes before you try again..." }

Expected Behavior
Show a clean, friendly UI message that:

  • Informs the user they've made too many requests
  • Explains they just need to wait a few minutes - offering them helpful next steps (e.g., "Try again in 5 minutes" or "Sign in with GitHub for higher limits")

Activity

  1. GowsiSM commented on Sep 1, 2026

    @GowsiSM
    ContributorAuthor

    @arnabnandy7 I’d love to work on this issue. I’ve already set things up locally and looked through the relevant error handling flow.

    Would you mind assigning this to me? I can work on the fix and open a PR soon. I’ll follow the existing shadcn/ui patterns for the error UI.

  2. added
    improvementFocused refinement to existing behavior, clarity, or user experience
    on Sep 1, 2026
  3. added this to the 1.2.0 milestone on Sep 1, 2026
  4. moved this from To Do to No status in Open issue portal developmenton Sep 1, 2026
  5. arnabnandy7 commented on Sep 1, 2026

    @arnabnandy7
    Owner

    @GowsiSM sure please create a new branch from current default and also refresh the setup since I've merged another feature just now as part of #71

  6. added 2 commits that reference this issue on Sep 3, 2026
    0a80027
    54a840e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

improvementFocused refinement to existing behavior, clarity, or user experience

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions