Fix: Always return HTTP 200 to display error cards in README (#860)#871
Merged
DenverCoder1 merged 3 commits intoDenverCoder1:mainfrom Feb 5, 2026
Merged
Fix: Always return HTTP 200 to display error cards in README (#860)#871DenverCoder1 merged 3 commits intoDenverCoder1:mainfrom
DenverCoder1 merged 3 commits intoDenverCoder1:mainfrom
Conversation
Owner
|
Thanks for looking into it! |
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
2 participants
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.
Description
When errors occur (user not found, API rate limit, missing token, etc.), the application returns HTTP 4xx/5xx status codes. GitHub's image proxy (Camo) rejects images with non-200 status codes, causing streak stats to display as broken images in READMEs instead of showing the error card.
This fix modifies renderOutput() to always return HTTP 200, ensuring error cards are properly displayed. The original error code is preserved in JSON responses for API consumers.
Fixes #860
Type of change