Google Git
Sign in
android / platform / frameworks / support / efa635006ba92f13e367ed45d7afe78d0d65059d
commitefa635006ba92f13e367ed45d7afe78d0d65059d[log] [tgz]
authorVineet Kumar <[email protected]>Tue Aug 30 10:00:54 2022 +0000
committerVineet Kumar <[email protected]>Thu Sep 01 03:16:17 2022 +0530
tree70e1dddbfa9af5f4524318e2b57269e9ca556ece
parentf303fb998e245b28ae1145ca3571e686f997820d [diff]
Revert "Revert "Featured Carousel feature in TV Compose.""

This reverts commit ab6c4b828736c71a91f14f81d8a45ff84503ea03.

Reason for revert: Reintroducing the Feature Carousel with code updated to
- use FocusDirection.Enter instead of FocusDirection.In
- cleaning up build.gradle as per the suggestion
- updating the test to fix the failure

Test: Tested manually by creating a sample app and have written
Integration Tests as well.

Relnote: "Adding the feature-carousel component to
          tv-compose library"

Change-Id: I7b629ac1bb828844ba6282a3dd1eb577dd994429
30 files changed
tree: 70e1dddbfa9af5f4524318e2b57269e9ca556ece
  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. credentials/
  28. cursoradapter/
  29. customview/
  30. datastore/
  31. development/
  32. docs/
  33. docs-public/
  34. docs-tip-of-tree/
  35. documentfile/
  36. draganddrop/
  37. drawerlayout/
  38. dynamicanimation/
  39. emoji/
  40. emoji2/
  41. enterprise/
  42. exifinterface/
  43. external/
  44. fakeannotations/
  45. fragment/
  46. frameworks/
  47. glance/
  48. gradle/
  49. graphics/
  50. gridlayout/
  51. health/
  52. heifwriter/
  53. hilt/
  54. inspection/
  55. interpolator/
  56. javascriptengine/
  57. leanback/
  58. lifecycle/
  59. lint-checks/
  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. privacysandbox/
  74. profileinstaller/
  75. recommendation/
  76. recyclerview/
  77. remotecallback/
  78. resourceinspection/
  79. room/
  80. samples/
  81. savedstate/
  82. security/
  83. sharetarget/
  84. slice/
  85. slidingpanelayout/
  86. sqlite/
  87. startup/
  88. swiperefreshlayout/
  89. test/
  90. testutils/
  91. text/
  92. tracing/
  93. transition/
  94. tv/
  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. libraryversions.toml
  114. LICENSE.txt
  115. OWNERS
  116. PREUPLOAD.cfg
  117. README.md
  118. settings.gradle
  119. studiow
  120. 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.