Google Git
Sign in
android / platform / frameworks / support / c062ed89bbfaa1e464f2d67a73496a85e8088812
commitc062ed89bbfaa1e464f2d67a73496a85e8088812[log] [tgz]
authorChris Craik <[email protected]>Wed May 30 16:18:02 2018 -0700
committerChris Craik <[email protected]>Wed Jun 27 09:36:07 2018 -0700
tree5d3d62a9a17caace8be42879ddc878e837970eb2
parenta972db7de7f80b523af5618c1d2478077ddc8825 [diff]
Fix positional prepend

When new PagedList latches in, copy the mLastLoad position from the
previous PagedList and transform it to the item's new position in the
PagedList. This position is passed (our best guess for) the most
recently accessed load position. This ensures that the next PagedList
to be created will be initialized with a position relevant to the
viewport.

This fixes a bug where the mLastLoad position would not be initialized
on a fresh PagedList if no in-viewport re-binds occur.

Fixes: 80149146
Test: ./gradlew :paging:runtime:cC

Change-Id: I3d84f8728e39171d899d7135eca7a97ad479a19b
7 files changed
tree: 5d3d62a9a17caace8be42879ddc878e837970eb2
  1. .idea/
  2. annotations/
  3. api/
  4. app-toolkit/
  5. appcompat/
  6. asynclayoutinflater/
  7. browser/
  8. buildSrc/
  9. car/
  10. cardview/
  11. collection/
  12. compat/
  13. content/
  14. coordinatorlayout/
  15. core/
  16. cursoradapter/
  17. customview/
  18. development/
  19. docs-fake/
  20. documentfile/
  21. drawerlayout/
  22. dynamic-animation/
  23. emoji/
  24. exifinterface/
  25. fragment/
  26. frameworks/
  27. gradle/
  28. graphics/
  29. gridlayout/
  30. heifwriter/
  31. interpolator/
  32. jetifier/
  33. leanback/
  34. leanback-preference/
  35. legacy/
  36. lifecycle/
  37. loader/
  38. localbroadcastmanager/
  39. media/
  40. media-widget/
  41. media2/
  42. mediarouter/
  43. navigation/
  44. paging/
  45. palette/
  46. percent/
  47. persistence/
  48. preference/
  49. print/
  50. recommendation/
  51. recyclerview/
  52. recyclerview-selection/
  53. room/
  54. samples/
  55. scripts/
  56. slices/
  57. slidingpanelayout/
  58. swiperefreshlayout/
  59. testutils/
  60. testutils-ktx/
  61. textclassifier/
  62. transition/
  63. tv-provider/
  64. versionedparcelable/
  65. viewpager/
  66. viewpager2/
  67. wear/
  68. webkit/
  69. work/
  70. .gitignore
  71. adding-support-library-as-included-build.md
  72. build.gradle
  73. gradle.properties
  74. gradlew
  75. include-composite-deps.gradle
  76. include-support-library.gradle
  77. LICENSE.txt
  78. OWNERS
  79. PREUPLOAD.cfg
  80. README.md
  81. settings.gradle
README.md

AOSP Support Library Contribution Guide

Accepted Types of Contributions

  • Bug fixes (needs a corresponding bug report in b.android.com)
  • 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

We are not currently accepting new modules, features, or behavior changes.

Checking Out the Code

NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.

Follow the “Downloading the Source” guide to install and set up repo tool, but instead of running the listed repo commands to initialize the repository, run the folowing:

repo init -u https://android.googlesource.com/platform/manifest -b ub-supportlib-master

Now your repository is set to pull only what you need for building and running support library. Download the code (and grab a coffee while we pull down 7GB):

repo sync -j8 -c

You will use this command to sync your checkout in the future - it’s similar to git fetch

Using Android Studio

Open path/to/checkout/frameworks/support/ in Android Studio. Now you're ready edit, run, and test!

If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.

If you see any warnings (red underlines) run Build > Clean Project.

Builds

Full Build (Optional)

You can do most of your work from Android Studio, however you can also build the full support library from command line:

cd path/to/checkout/frameworks/support/
./gradlew createArchive

Building Support Library as part of your App build

If you intend to repeatedly make changes to Support Library and to wish to see the results in your app, and you don't want to have to repeatedly build them as separate Gradle projects, you can configure your app build to build Support Library too

Running Tests

Single Test Class or Method

  1. Open the desired test file in Android Studio.
  2. Right-click on a test class or @Test method name and select Run FooBarTest

Full Test Package

  1. In the project side panel open the desired module.
  2. Find the directory with the tests
  3. Right-click on the directory and select Run android.support.foobar

Running Sample Apps

Support library has a set of Android applications that exercise support library code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.

These applications are named support-*-demos (e.g. support-4v-demos or support-leanback-demos. You can run them by clicking Run > Run ... and choosing the desired application.

Making a change

cd path/to/checkout/frameworks/support/
repo start my_branch_name .
(make needed modifications)
git commit -a
repo upload --current-branch .

If you see the following prompt, choose always:

Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?

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)