commit | bc4d0b0964aaa1daee6e0ef2cfceb231350dc093 | [log] [tgz] |
---|---|---|
author | Elif Bilgin <elifbilgin@google.com> | Sun Jun 06 12:02:05 2021 -0700 |
committer | Elif Bilgin <elifbilgin@google.com> | Sun Jun 06 12:02:05 2021 -0700 |
tree | c51062746e2c893a60d457077fc8eb388ef0ae39 | |
parent | 9fcd3c9e07dfe9167a198954763676a8084d51c6 [diff] |
Resolving issue of improper handling of indexes in auto migrations. Fixed two issues in this CL: 1) When a brand new table is added in the new database version, only the CREATE TABLE statement was used in constructing the new table. This was an invalid approach as the CREATE TABLE SQL statements do not include the statements required to create the indexes associated with this table. Therefore, even if there were indexes in the new table, the statements for adding them to the table would not be added in AutoMigrationWriter. This issue was only valid for the case of indexes, as foreign keys are included in the CREATE TABLE statements, and views are destroyed and recreated by our implementation independent of CREATE TABLE (regardless of any changes). 2) When we check for new added columns, we have logic in place that avoids processing any new columns detected in a table that has already been discovered as a "complex changed table", as this table will be destroyed and recreated from scratch already, and the new added columns will be handled automatically in this process. In the previous logic, we were conducting this check by looking up the name of the "toTable" in the map of complex changed tables. This was incorrect as the map is keyed by the table names in the "from" version of the database, therefore if a table was renamed and included complex changes and had a new column added to it, this check would fail (as the table would not be found in the map). A new Entity has been added to AutoMigrationDb to check for these cases. Bug: 189726437 Test: AutoMigrationTest.java Change-Id: I2554abe0e5ea2d5c5031ab6112862c25b7d5879c
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.