commit | f2a6bc1a6937e659b476276fc34d59b0d43fe649 | [log] [tgz] |
---|---|---|
author | Ian Lake <ilake@google.com> | Tue Aug 15 23:47:52 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Aug 25 05:00:19 2023 +0000 |
tree | 600e37658977110a196f651bfe99b2799fbafef5 | |
parent | 5176187be21eaef7a2083696d909af5bafe8aa5c [diff] |
Ensure that asSnapshot works with PagingData.from When using the PagingData.from() overload that does not define any LoadStates, asSnapshot was unable to determine when loading has finished. By listening for the completion of the Flow<PagingData>, we can verify that loading has completed, thus avoiding cases where we never get any load state changes. BUG: 295039974 Test: updated tests pass Relnote: "Fixed an issue where the `asSnapshot()` API of the Paging Testing artifact would hang when passed a Flow built using `PagingData.from(List)` since `asSnapshot()` would not have any information on when loading has finished (unlike the `PagingData.from(List, LoadStates)` overload). This workaround only works for completable Flows (e.g., a `flowOf(PagingData.from(...))`). For non-completable Flows (e.g., `MutableStateFlow`, use the `PagingData.from` overload that provides `LoadStates`." (cherry picked from https://android-review.googlesource.com/q/commit:ab18122db4557f55659a9ab273199b7380352b56) (cherry picked from https://android-review.googlesource.com/q/commit:56c617ec0bdc450e9c3fa3aa072347d5cc23b697) Merged-In: I502c3653398feaf1a2dba34072cf89eb58126670 Change-Id: I502c3653398feaf1a2dba34072cf89eb58126670
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()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.