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")
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:
Expected Behavior
Show a clean, friendly UI message that: