fix: make ImageExport export all cell states correctly
#425
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
ImageExport export content
Previously, the visitor function always used the initial state passed at the beginning of the recursion instead of the state of the recursion step. So, nothing was exported. Add new tests to better cover `ImageExport`: - check overlays - export using `SvgCanvas2D` in addition to `XmlCanvas2D`
b036604 to
f670d7d
Compare
ImageExport export contentImageExport export all cell states correctly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Previously, the visitor function always used the initial state passed at the beginning of the recursion instead of the state of the recursion step. So, nothing was exported.
Add new tests to better cover
ImageExport:SvgCanvas2Din addition toXmlCanvas2DNotes
Depends on #423