Google Git
Sign in
android / platform / frameworks / support / c2ac49c6b3b47d67ed706f6bd2a49aebdfa6af07
commitc2ac49c6b3b47d67ed706f6bd2a49aebdfa6af07[log] [tgz]
authorChuck Jazdzewski <chuckj@google.com>Mon Apr 18 14:14:47 2022 -0700
committerChuck Jazdzewski <chuckj@google.com>Mon Apr 18 15:22:18 2022 -0700
treec455e02510d1b00b25dca6701d8bfd0642296846
parent90b05d72935ba8d80451bf9b24b4fdc88acd0b12 [diff]
Add support for using composable target annotation at file scope

`@ComposableTarget` and annotations marked `@ComposableTargetMarker` are
now looked for as `@file:` annotations. Adding a composable target
annotation at the file scope declares that all `2Compsoable` functions
in this file are, by default, assumed to be targetting the applier implied
by the annotations. For examplea, using `@file:UiComposable` will cause
all `@Composable` functions in the file to be assumed to be targetting
the Compose UI applier.

Relnote: """The `@ComposableTarget` annotation and annotations marked by
`@ComposableTargetMarker` can now be used at the file scope using the
`@file` prefix. Using a target annotation at the file scope will cause the
compiler to assume all composable functions in the file are intended to be
targeth the associated applier. For example, using `@file:UiComposable`
declares that all `@Composable` functions target the Compose UI
applier. A function that needs to target another applier must explicity
supply the target marker annotation for the desired applier.
"""

Fixes: 228078200
Test: ./gradlew :compose:c:c-h:i-t:tDUT
Change-Id: I40804e71dcc931b788c101a0be90ae1d6fc7eba1
15 files changed
tree: c455e02510d1b00b25dca6701d8bfd0642296846
  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. browser/
  14. buildSrc/
  15. buildSrc-tests/
  16. busytown/
  17. camera/
  18. car/
  19. cardview/
  20. collection/
  21. collection2/
  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. jetifier/
  56. leanback/
  57. lifecycle/
  58. lint-checks/
  59. lint-demos/
  60. loader/
  61. media/
  62. media2/
  63. mediarouter/
  64. metrics/
  65. navigation/
  66. paging/
  67. palette/
  68. percentlayout/
  69. placeholder-tests/
  70. playground-common/
  71. preference/
  72. print/
  73. profileinstaller/
  74. recommendation/
  75. recyclerview/
  76. remotecallback/
  77. resourceinspection/
  78. room/
  79. samples/
  80. savedstate/
  81. security/
  82. sharetarget/
  83. slice/
  84. slidingpanelayout/
  85. sqlite/
  86. startup/
  87. swiperefreshlayout/
  88. temp/
  89. template/
  90. test/
  91. testutils/
  92. text/
  93. tracing/
  94. transition/
  95. tvprovider/
  96. vectordrawable/
  97. versionedparcelable/
  98. viewpager/
  99. viewpager2/
  100. wear/
  101. webkit/
  102. window/
  103. work/
  104. .gitignore
  105. .mailmap
  106. build.gradle
  107. cleanBuild.sh
  108. code-review.md
  109. CONTRIBUTING.md
  110. gradle.properties
  111. gradlew
  112. include-composite-deps.gradle
  113. include-support-library.gradle
  114. libraryversions.toml
  115. LICENSE.txt
  116. OWNERS
  117. PREUPLOAD.cfg
  118. README.md
  119. settings.gradle
  120. studiow
  121. 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.