fix: prevent markdown rendering error by ensuring string input#1612
Merged
Blastoplex merged 2 commits intomainfrom Feb 16, 2026
Merged
fix: prevent markdown rendering error by ensuring string input#1612Blastoplex merged 2 commits intomainfrom
Blastoplex merged 2 commits intomainfrom
Conversation
Guard against null or undefined markdown input by defaulting to empty string before rendering. This fixes the "Input data should be a String" error caused when markdown content is missing or null in DialogMessageItem, MarkedDown component, and ToolReturnParsedItem components.
Collaborator
|
How did you arrive at this fix? Did you prove that one of these was null or undefined in the problem cases? |
Contributor
Author
|
yep validating atm. per the types, its expected that the message content could be null/undefined Will pop in some tests also |
Contributor
Author
amarg-at
approved these changes
Feb 16, 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.

Guard against null or undefined markdown input by defaulting to empty string before rendering. This fixes the "Input data should be a String" error caused when markdown content is missing or null in DialogMessageItem, MarkedDown component, and ToolReturnParsedItem components.
https://atlassian.slack.com/archives/C09DA8EUW9F/p1770768423830179
devloped in RDiJ and tested with npm run test:react