commit | e53eee76cf41dd48055dba22c665d99f2ae627db | [log] [tgz] |
---|---|---|
author | Paul Duffin <paulduffin@google.com> | Thu Feb 08 22:51:03 2024 +0000 |
committer | Paul Duffin <paulduffin@google.com> | Fri Feb 09 09:37:20 2024 +0000 |
tree | 89cd8ec96af66cb76a7cd186ad5688ae4f867dd6 | |
parent | 5dda4ea48e68d10c8c5cc04d5f4ee299295e1835 [diff] |
Fixed signature file issue with Collection bulk operation overrides Previously, due to an error in Psi and a workaround for some, possibly separate issue, that worked well enough to look ok at a superficial level, some incorrect signatures were written out for some Collection bulk operations, i.e. `containsAll`, `removeAll`, `retainAll`. They should have a signature that looks something like: ``` boolean retainAll(Collection<? extends X>); ``` Where `X` can be a type parameter or a specific class. Instead what it did was just write out something like: ``` boolean retainAll(Collection<E>); ``` No wildcard, and always `E`, even if the actual type was different like say `T`, or `androidx.compose.ui.text.intl.Locale`. The reason it chose `E` was because it was given a raw type that it knew should have some type arguments and it just resolved the class and used its type parameters as the type arguments. As `Collection` is defined as `Collection<E>` so `E` was chosen. More details can be found at https://r.android.com/2953645 in a comment in the `PsiTypeItem.kt` file. It was not detected when reading the API signature file as the API signature parsing code would just treat `E` as if it was an unknown class in `java.lang` if it did not recognize it as a type parameter. RelNote: N/A Bug: 324317136 Test: ./gradlew Change-Id: I391461ca3af62515c9bc6848c973b674c9329e54
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.