Repository navigation
Fix: Guard HyperBot follow-up messages against null API response - #210
Merged
Merged
Conversation
kevinhermawan
approved these changes
Nov 11, 2026
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.
hyperjump.tech Pull Request
What does this PR solve?
Uncaught TypeError: Cannot read properties of null (reading 'length')right after sending a message.data: null(or nodatakey), leaving thefollowUpMessagesstate asnull.How does this PR solve this problem?
fetchFollowUpMessagesnow returnsdata.data ?? [], matching the existing null-safe pattern used byfetchPreviousMessages.(followUpMessages ?? []).length > 0as a defense-in-depth guard.How to test this PR?
/en/oneai) and start a chat.{ data: null }and verify the widget still renders fine.Are there any screenshots/videos?
None