fix: ASCII backend generates PDF binary content instead of text output #222
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.
Summary
Test plan
Details
The bug occurred when a figure switched backends multiple times (e.g., ASCII -> PDF -> ASCII). The
switch_backend_if_needed()function was hardcodingcurrent_backend = 'ascii'instead of checking what backend was actually allocated. This caused the function to skip backend switching when it should have switched from PDF back to ASCII for .txt files.The fix uses
select typeto examine the polymorphic backend object and correctly identify whether it's anascii_context,pdf_context,png_context, etc.🤖 Generated with Claude Code