fix: API error handling with user-facing messages and retry#188
Merged
fix: API error handling with user-facing messages and retry#188
Conversation
TipHistory: Add error state with network/contract error differentiation and retry button. Validate API response status before parsing JSON. PlatformStats: Improve error message to differentiate network vs contract errors. RecentTips: Improve error message to differentiate network errors from API response errors. All three components now show clear user-facing error messages with retry buttons when the Stacks API is unavailable or returns errors.
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
1 participant
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.
Closes #80
Changes
errorstate, show clear error message with retry button when Stacks API fetch fails. Validate API response status before parsing JSON.All three data-fetching components now: