Google Git
Sign in
android / platform / frameworks / support / 22c62178214a63902a4634b084c3d0ba080d2b19
commit22c62178214a63902a4634b084c3d0ba080d2b19[log] [tgz]
authorDaniel Santiago Rivera <[email protected]>Fri May 27 11:43:56 2022 -0700
committerDaniel Santiago Rivera <[email protected]>Tue May 31 09:57:33 2022 -0700
treec3a53da925a4e0f1ded8b9dc7613a59698c4bc21
parentf5d070f134c927cd00f7a5d8d4484fc91db07883 [diff]
Expose RoomDatabase getters via properties.

When RoomDatabase was in Java, Kotlin callers could use the property syntax to get some of the fields, `openHelper`, `queryExecutor`, etc. By moving Room to Kotlin and keeping the getters as function and the fields internal or private, we break source incompatibility making the migration harder. This changes makes it so that we use properties, keeping ABI compatibility and source compatibility at the cost of extra internal properties.

Relnote: "Fix a Kotlin source incompatible change for getter / properties of getOpenHelper, getQueryExecutor and getTransactionExecutor."
Bug: 234152465
Test: Existing
Change-Id: Iad0ac5775730c80127f57fe6eec58796c0aff5d6
15 files changed
tree: c3a53da925a4e0f1ded8b9dc7613a59698c4bc21
  1. .github/
  2. .idea/
  3. activity/
  4. ads/
  5. annotation/
  6. appcompat/
  7. appsearch/
  8. arch/
  9. asynclayoutinflater/
  10. autofill/
  11. benchmark/
  12. biometric/
  13. bluetooth/
  14. browser/
  15. buildSrc/
  16. buildSrc-tests/
  17. busytown/
  18. camera/
  19. car/
  20. cardview/
  21. collection/
  22. compose/
  23. concurrent/
  24. contentpager/
  25. coordinatorlayout/
  26. core/
  27. cursoradapter/
  28. customview/
  29. datastore/
  30. development/
  31. docs/
  32. docs-public/
  33. docs-tip-of-tree/
  34. documentfile/
  35. draganddrop/
  36. drawerlayout/
  37. dynamicanimation/
  38. emoji/
  39. emoji2/
  40. enterprise/
  41. exifinterface/
  42. external/
  43. fakeannotations/
  44. fragment/
  45. frameworks/
  46. glance/
  47. gradle/
  48. gridlayout/
  49. health/
  50. heifwriter/
  51. hilt/
  52. ink/
  53. inspection/
  54. interpolator/
  55. leanback/
  56. lifecycle/
  57. lint-checks/
  58. lint-demos/
  59. loader/
  60. media/
  61. media2/
  62. mediarouter/
  63. metrics/
  64. navigation/
  65. paging/
  66. palette/
  67. percentlayout/
  68. placeholder-tests/
  69. playground-common/
  70. preference/
  71. print/
  72. profileinstaller/
  73. recommendation/
  74. recyclerview/
  75. remotecallback/
  76. resourceinspection/
  77. room/
  78. samples/
  79. savedstate/
  80. security/
  81. sharetarget/
  82. slice/
  83. slidingpanelayout/
  84. sqlite/
  85. startup/
  86. swiperefreshlayout/
  87. test/
  88. testutils/
  89. text/
  90. tracing/
  91. transition/
  92. tvprovider/
  93. vectordrawable/
  94. versionedparcelable/
  95. viewpager/
  96. viewpager2/
  97. wear/
  98. webkit/
  99. window/
  100. work/
  101. .gitignore
  102. .mailmap
  103. build.gradle
  104. cleanBuild.sh
  105. code-review.md
  106. CONTRIBUTING.md
  107. gradle.properties
  108. gradlew
  109. include-composite-deps.gradle
  110. libraryversions.toml
  111. LICENSE.txt
  112. OWNERS
  113. PREUPLOAD.cfg
  114. README.md
  115. settings.gradle
  116. studiow
  117. TEXT_OWNERS
README.md

Android Jetpack

Revved up by Gradle Enterprise

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.

Contribution Guide

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:

Code Review Etiquette

When contributing to Jetpack, follow the code review etiquette.

Accepted Types of Contributions

  • Bug fixes - needs a corresponding bug report in the Android Issue Tracker
  • Each bug fix is expected to come with tests
  • Fixing spelling errors
  • Updating documentation
  • Adding new tests to the area that is not currently covered by tests
  • New features to existing libraries if the feature request bug has been approved by an AndroidX team member.

We are not currently accepting new modules.

Checking Out the Code

Head over to the onboarding docs to learn more about getting set up and the development workflow!

Continuous integration

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.

Password and Contributor Agreement before making a change

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

Getting reviewed

  • After you run repo upload, open r.android.com
  • Sign in into your account (or create one if you do not have one yet)
  • Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)

Handling binary dependencies

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.