commit | 04b0474a288dfd30b0e82f3e5259920e867b15fe | [log] [tgz] |
---|---|---|
author | Yigit Boyar <yboyar@google.com> | Fri Feb 26 12:04:07 2021 -0800 |
committer | Yigit Boyar <yboyar@google.com> | Mon Mar 01 17:00:37 2021 -0800 |
tree | 22e103bb5e969441bd179a5a6af144a167f15287 | |
parent | 49fda86f2b8eaea25cc67162f6e13b05d9a110eb [diff] |
Use lazy invalidation tracking for Paging 3 This CL works around a bug in Paging3 integration where using Paging3 with Room could cause main thread queries. This is a workaround, not a proper fix. In Paging2, we had a data source factory class and its create method was always called on a background thread. It also had very strict invalidation requirements such that if database changed underneath, we had to detect it before returning any data. In Paging3, the factory does not exist anymore as a concrete class so a common implentation is to do: ``` val myPager = Pager(...) { myDao.createPagingSource() } ``` That code is invoked in the collection dispatcher which is commonly the main dispatcher. Because we are still using the Paging2 APIs internally, this would end up creating the old data source impl (Paging2) and then wrap it into a Paging3 PagingSource. Unfortunately, creating Paging2 DataSource requires syncronizing invalidation trackers with the backing database, hence possibly a main thread query. The ultimate plan for Paging3 support is to create a room-paging artifact. This CL is a quick fix for the problem above where we change the behavior of the LimitOffsetDataSource not to register an invalidation when it is created, instead, register it when we run the very first query. This way, it is more lazy (good) and won't try to load the data on the main thread (Paging3 wrapper for Paging2 data source takes care of moving load functions to the background thread). Bug: 181221318 Test: PagingSourceTest Relnote: "Fixed a bug where creating PagingSource on the main thread could trigger an ANR." Change-Id: I42b74e397bcf717f509b1d53203d2edced89afb0
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.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
repo
(Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see the Repo Command Reference)mkdir ~/bin PATH=~/bin:$PATH curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo chmod a+x ~/bin/repo
git config --global user.name "Your Name" git config --global user.email "you@example.com"
mkdir androidx-main cd androidx-main
repo
command to initialize the repository.repo init -u https://android.googlesource.com/platform/manifest -b androidx-main --partial-clone --clone-filter=blob:limit=10M
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
To open the project with the specific version of Android Studio recommended for developing:
cd path/to/checkout/frameworks/support/ ANDROIDX_PROJECTS=MAIN ./gradlew studio
and accept the license agreement when prompted. Now you're ready to edit, run, and test!
You can also the following sets of projects: ALL
, MAIN
, COMPOSE
, or FLAN
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
.
You can do most of your work from Android Studio, however you can also build the full AndroidX library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
You can build maven artifacts locally, and test them directly in your app:
./gradlew createArchive
And put the following at the top of your ‘repositories’ property in your project build.gradle
file:
maven { url '/path/to/checkout/out/androidx/build/support_repo/' }
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.
Run FooBarTest
Run androidx.foobar
The AndroidX repository has a set of Android applications that exercise AndroidX 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 either <libraryname>-integration-tests-testapp
, or support-\*-demos
(e.g. support-v4-demos
or support-leanback-demos
). You can run them by clicking Run > Run ...
and choosing the desired application.
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
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)?
If the upload succeeds, you'll see output like:
remote: remote: New Changes: remote: https://android-review.googlesource.com/c/platform/frameworks/support/+/720062 Further README updates remote:
To edit your change, use git commit --amend
, and re-upload.
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.