Validate bridge API response for get_account_posts to prevent runtime errors #524
Conversation
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
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.
Fixes ECENCY-NEXT-W4W. The issue was that: Hive API returned non-array truthy value; code lacked runtime validation, causing
.mapon object.The bridge API
get_account_postsendpoint can return null or a non-array value in some cases. This change adds a check to ensure that the response is an array before attempting to map over it, preventing runtime errors.This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 32664
Not quite right? Click here to continue debugging with Seer.