Print collection content in ComposePrintToString to stabilize output in Dump screenshots. #642
Conversation
This file contains 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
|
Snapshot diff report
|
siarhei-luskanau
force-pushed
the
ComposePrintToString3
branch
from
51fcf81 to
6c3403c
Compare
…in Dump screenshots.
siarhei-luskanau
force-pushed
the
ComposePrintToString3
branch
from
6c3403c to
e9d6c15
Compare
|
Thank you for ensuring Roborazzi's determinism! |
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.
Dump screenshot has node properties. Sometime Roborazzi generates new screenshots (or fails verification) due the node print the
androidx.compose.ui.semantics.CollectionInforeference value instead of content. This Pull Request add the output sorting to avoid the issue.