commit | 5d5558805f5a264a6bbb0b643431c4aae92e4fab | [log] [tgz] |
---|---|---|
author | Brad Corso <bcorso@google.com> | Sat Jun 25 20:20:28 2022 -0700 |
committer | Brad Corso <bcorso@google.com> | Tue Jun 28 02:48:12 2022 +0000 |
tree | e302de6cd9a6f968e8c7fa4e05500792d5f27b7a | |
parent | 52f578302ca1bcf76618abbc64fe4ab1441b72a8 [diff] |
Add new tests for generic and inherited types. This CL adds tests for coverage of type names of generic and inherited types in different scenarios. The main purpose of the test is to ensure that XProcessing is reporting the same type name for both KSP and KAPT. This can be a bit tricky because it means we have to match types in kotlin source files with the type names that KAPT generates for those source files. Note: there are currently cases where the type name differs between KSP and KAPT. This CL isn't meant to fix those cases but simply add coverage for them. They will be fixed in a separate CL. Bug: 237280547 Test: TypeInheritanceTest Change-Id: I316954907e549296944321e684055486856082a0
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.