[fix]: artifact actionlist rendering in chat #430
+94
−2
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.
Fix Artifact Rendering in Chat Messages
Problem
When chat messages contain Artifact components (like ActionLists) wrapped in code fences (```), they are rendered as plain code blocks instead of rendering via Artifact.tsx component.
Root Cause
ReactMarkdown processes code-fenced content before component rendering, causing the boltArtifact elements to be treated as plain text within code blocks rather than being passed to the Artifact component.
Solution
Added preprocessing step to remove code fence markers specifically around artifact elements:
Alternative Approach Considered
Explored handling at the component level through ReactMarkdown's AST:
Why Current Solution Was Chosen
Changes
Before
After
Impact
Testing
stripCodeFenceFromArtifact