fix(deps): update showkase to v1.0.0-kotlin1.5.30-1 #521
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.0.0-beta17
->1.0.0-kotlin1.5.30-1
1.0.0-beta17
->1.0.0-kotlin1.5.30-1
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
airbnb/Showkase (com.airbnb.android:showkase-processor)
v1.0.0-beta18
Compare Source
You can now create another annotation class that's annotated with
@Preview
and Showkase will ensure that the@Preview
properties are applied whenever you use the custom annotation. Here's an exampleThis was contributed by @oas004 and required a lot of diligence 👏🏻
showkase-screenshot-testing-paparazzi
that provides a mechanism to automate screenshot testing for your codebase using Showkase + Paparazzi (https://github.com/airbnb/Showkase/pull/294).Assuming that you were already using Showkase, you just need 3 lines of code in the
test
sourceset of your root module to automatically screenshot test all your previews in the default configuration.In our own usage, we've found issues with using Paparazzi when the codebase has a large number of screenshot and haven't quite figured out what's causing it (https://github.com/cashapp/paparazzi/issues/630). As a result, try at your own risk. Having said that, we are really keen on resolving the linked issue and deploying this. If you have any insights about this issue, please reach out!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.