commit | 4194095366032c1c06d9e472e4e78b822c82cbe6 | [log] [tgz] |
---|---|---|
author | elifbilgin <elifbilgin@google.com> | Thu Feb 09 15:08:57 2023 -0800 |
committer | Elif Bilgin <elifbilgin@google.com> | Wed Mar 15 18:56:30 2023 +0000 |
tree | e133eb68a9298cd2005bfe6de4a4480598bc0345 | |
parent | f9883802bda9c56c6a05f5dad5c10ba56b4e299b [diff] |
Supporting value classes in Room for KSP. Value classes are now supported for KSP with Kotlin codegen in Room. In KAPT stubs and in bytecode the places where the value class is used is replaced by the underlying type. This is the reason why we can't tell in KAPT or javac if the type is a value class without looking at the metadata. We have filed b/273592453 to further investigate this and figure out a solution for handling this case. We are planning to follow-up and add a check such that, if user is on KAPT, straight out error, if user is on KSP gen Java, hint to @JvmInline and @JvmName requirements (if we can conclusively say they work this way) to use value classes with Java codegen and point to full-support with Kotlin codegen. Bug: 124624218 Bug: 272820290 Test: TypeAdapterStoreTest.kt Change-Id: I0a380ada951df776ed7bcb96757b86103743b0c5
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.