fix(deps): update roborazzi to v1.37.0 #760
Merged
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.
This PR contains the following updates:
1.34.0
->1.37.0
1.34.0
->1.37.0
1.34.0
->1.37.0
1.34.0
->1.37.0
1.34.0
->1.37.0
Release Notes
takahirom/roborazzi (io.github.takahirom.roborazzi)
v1.37.0
Compare Source
Bug Fixes and Workarounds
Compose AlertDialog Support
Support for capturing Alert Dialogs has been fixed, ensuring correct screenshot display.
captureScreenRoboImage()
, which merges all windows, is now used only when multiple windows are present. Thanks to @ashughes for reporting this and to @mhidaka and @hiroaki404 for bringing it to my attention at a Japan Android testing event.Workaround for Overlap Handling for SDK 35 Compose Screenshots
Problem
When updating to SDK 35 and using the default theme, the ActionBar is included in screenshots, leading to overlap when using
createComposeRule()
. This occurs becausecreateComposeRule()
uses the default theme by default. Thank you for letting me know about this, @keyboardsurfer!I have filed an issue for this: https://issuetracker.google.com/issues/383368165
Why this happens
SDK 35 enforces edge-to-edge display, which means it does not provide automatic padding for the ActionBar.
How Roborazzi currently workarounds this
Roborazzi now automatically hides the ActionBar when taking screenshots on SDK 35 and higher. This functions similarly to
view.getActivity()?.actionBar?.hide()
. However, this workaround may cause performance issues and should not be relied upon. Roborazzi outputs warning logs with alternative suggestions. Thank you to @sergio-sastre for advising on this workaround!If you need to include the ActionBar in screenshots, Roborazzi provides a flag,
roborazzi.compose.actionbar.overlap.fix=false
, that can be added to yourgradle.properties
file.What should we do?
A permanent solution will likely require changes from Google. In the meantime, adding
<application android:theme="@​style/Theme.AppCompat.Light.NoActionBar" />
to the module'ssrc/test/AndroidManifest.xml
file changes the Activity's default theme and resolves the issue. Thank you to @mattinger for finding this!https://github.com/takahirom/roborazzi/issues/598#issuecomment-2533372700
Stabilized Output for Dump Screenshots
Thanks to @siarhei-luskanau for contributing an improvement that reduces unnecessary diffs for the Roborazzi dump feature.
New Features
Add
inspectionMode()
for Compose PreviewsThanks to @YusukeMoriJapan's contribution,
inspectionMode()
is now available inRoborazziComposeOptions
. This is particularly useful when working with libraries that have specific preview implementations. This mode is off by default to maintain high fidelity.Here's how to enable it:
What's Changed
New Contributors
Full Changelog: takahirom/roborazzi@1.36.0...1.37.0
v1.36.0
Compare Source
Behavior Changes to
roborazzi.outputDir.set(file("somedir"))
inbuild.gradle
Previously, when modifying
roborazzi.outputDir
, such as setting it tosrc/screenshots
, this option also affected the paths for comparison images, likefoo_compare.png
. This behavior often caused issues, such as unintentionally saving comparison images to version control systems (e.g., Git). To address this, we have discontinued this behavior. Comparison images are now saved inbuild/outputs/roborazzi
by default, while the behavior for reference images remains unchanged.For users who wish to customize the path for comparison images, we have introduced a new option:
roborazzi.compare.outputDir
.While I don't believe there are strong use cases for this, if you want to save the comparison images in a custom directory as you did before, you can specify
roborazzi.compare.outputDir
as follows:I believe this adjustment will be highly beneficial for most use cases involving changes to
outputDir
.What's Changed
Full Changelog: takahirom/roborazzi@1.35.0...1.36.0
v1.35.0
Compare Source
Add support for heightDp, widthDp, showBackground, and backgroundColor of Compose Preview parameters
We have introduced Experimental Compose Preview Support in 1.22.0, but it does not yet support all parameters of the
@Preview
annotation. Thanks to @sergio-sastre 's pull request, the Experimental Compose Preview Support now includes support for heightDp, widthDp, showBackground, and backgroundColor.Introduce RoborazziComposeOptions
To accommodate the changes in preview parameters, we’ve made the API more flexible.
We’ve added the
RoborazziComposeOptions
parameter toComposablePreview<AndroidPreviewInfo>.captureRoboImage()
and the composable function version,captureRoboImage{}
. Previously, the API was limited; for example, you couldn’t access the ActivityScenario or the composable function directly. Now, you have full control over these components. Thank you for your code review @sergio-sastreHere’s an example of a custom option:
Breaking Change:
fun ComposablePreview<AndroidPreviewInfo>.applyToRobolectricConfiguration()
is now deprecated and marked as an errorAs part of our updates to how composables are configured, the
applyToRobolectricConfiguration()
function is now deprecated and marked as an error. Instead, you can use one of the following alternatives:previewInfo.toRoborazziComposeOptions().apply(scenario, composeContent)
ComposablePreview<AndroidPreviewInfo>.captureRoboImage(roborazziComposeOptions)
We believe this feature is not widely used, and the migration should be straightforward. However, if you encounter any issues, please don’t hesitate to reach out.
Breaking Change: Composable
captureRoboImage{}
Behavior ChangeWe intended to use a transparent background for the Compose
captureRoboImage
function, but it was not applied due to Robolectric's resource merging mechanism. We have fixed this behavior; however, this change will result in altered screenshots. You can now specify the background in the newRoborazziComposeOptions
as we had previously.What's Changed
Full Changelog: takahirom/roborazzi@1.34.0...1.35.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "every 4 hour after 00:00 and before 23:59 every day" in timezone Asia/Tokyo.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.