| commit | a884270c1a1b8ce55e12fcebf6387c299ceee001 | [log] [tgz] |
|---|---|---|
| author | Zach Klippenstein <klippenstein@google.com> | Tue Nov 22 12:36:53 2022 -0800 |
| committer | Zach Klippenstein <klippenstein@google.com> | Tue Nov 22 12:51:18 2022 -0800 |
| tree | 7a22645232123c0cc555e0c9df7bef35448aeb99 | |
| parent | d182d8af38f407dcb35599126c6c7534381abe25 [diff] |
Refactor some animation tests to be more imperative and deterministic. AnimatedContentTest.AnimatedContentSlideInAndOutOfContainerTest: The assertions were written inside a LaunchedEffect for each branch of the transition. The test actually runs two transitions in a row, with different assertions for each run, but those were all embedded in the same LaunchedEffect and triggered by comparing and setting some state in a recomposition. This made the test hard to follow and update. I pulled the state writes that trigger the animations, as well as the assertions, out and used explicit advanceByFrame calls. AnimatedVisibilityTest.testTransitionExtensionAnimatedVisibility: The test was using tween animations with the default easing, which is harder to write assertions around because due to the curve the animation can reach final values before the animation duration is complete. I changed the animation to use LinearEasing instead, and updated the test assertions accordingly (e.g. the content will be completely removed from the composition when hidden instead of being measured with zero size). Other changes are using Truth for assertions and auto-formatting from Android Studio. Test: AnimatedContentTest, AnimatedVisibilityTest Change-Id: Iee546c24ab1ead7805968e3cf5a92ca6df6fcf10
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.* package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal and prebuilts/androidx/external directories in your checkout. All the dependencies in these directories are also available from google(), jcenter(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.
