commit | 3680e25632ab3511e476031f1f19df1fcfb08346 | [log] [tgz] |
---|---|---|
author | Ian Lake <[email protected]> | Mon Feb 13 19:56:05 2023 +0000 |
committer | Ian Lake <[email protected]> | Tue Feb 14 16:14:22 2023 +0000 |
tree | e167c65a24b78f1a35cc7812957f679e3b2eb1e2 | |
parent | f60c1f22dba35b6fdf8be69f188f017e1cd36b4c [diff] |
Use initialized value from LiveData for first composition Previously, observeAsState(initial) would always show the initial value on the first composition, even if the LiveData already had a valid value set on it. By using the LiveData.isInitialized check, we can distinguish between the cases where no value has ever been set on the LiveData (which case we'll use the initial value passed to the function) versus the cases where a value has already been set on the LiveData. This ensures that even on the first composition, a LiveData with a valid value will have the correct State emitted. Relnote: "The `LiveData.observeAsState(initial)` API now correctly uses the `value` already set on the LiveData in the first composition. The `initial` value passed to this function is now only used if `LiveData.isInitialized` returns false (i.e., no value has ever been set on the `LiveData`). Note that for LiveData types that have a non-null generic type (e.g., `LiveData<String>`), it is your responsibility to ensure only non-null values are set on the `LiveData`." Test: new preferInitializedValueInFirstComposition test BUG: 180450267 BUG: 214434197 Change-Id: Ie8f494ffcaed65c7ae8f08dabb8304be6721cd0f
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.