Gitiles
Code Review Sign In
review.blissroms.org / platform_frameworks_support / 9f869feea7a58c274864e93ddcc5e87ea6877417
commit9f869feea7a58c274864e93ddcc5e87ea6877417[log] [tgz]
authorKodlee Yin <kodlee@google.com>Mon Dec 18 21:34:43 2017 -0800
committerKodlee Yin <kodlee@google.com>Tue Dec 19 17:08:40 2017 -0800
treeaff3304fbc9618d97466e0ad36cf04fb0ff40dd1
parent130670524f480439f3ce0fc721e53e9348ca3a33 [diff]
Add MessagingStyle#isGroupConversation().

This will allow apps to mark a Notification's MessagingStyle as a group
conversation. This is useful because the current implementation
overloads MessagingStyle#conversationTitle; which, when not null,
implies a group conversation. Instead of relying on this implicit
contract, we include this change's explicit field.

Test: ./gradlew support-compat:connectedCheck --info --daemon
Bug: 67717177, 70725009
Change-Id: I73f7d11d084b86e8b92098281855748edb8b6136
3 files changed
tree: aff3304fbc9618d97466e0ad36cf04fb0ff40dd1
  1. .idea/
  2. annotations/
  3. api/
  4. app-toolkit/
  5. buildSrc/
  6. car/
  7. compat/
  8. content/
  9. core-ui/
  10. core-utils/
  11. customtabs/
  12. design/
  13. development/
  14. dynamic-animation/
  15. emoji/
  16. exifinterface/
  17. fragment/
  18. frameworks/
  19. gradle/
  20. graphics/
  21. jetifier/
  22. leanback/
  23. lifecycle/
  24. media-compat/
  25. paging/
  26. percent/
  27. persistence/
  28. preference-leanback/
  29. recommendation/
  30. recyclerview-selection/
  31. room/
  32. samples/
  33. scripts/
  34. slices/
  35. testutils/
  36. transition/
  37. tv-provider/
  38. v13/
  39. v14/
  40. v4/
  41. v7/
  42. viewpager2/
  43. wear/
  44. webkit/
  45. webkit-codegen/
  46. .gitignore
  47. Android.mk
  48. build.gradle
  49. CleanSpec.mk
  50. gradle.properties
  51. gradlew
  52. LICENSE.txt
  53. makeFlatfootRepo.sh
  54. OWNERS
  55. pathmap.mk
  56. PREUPLOAD.cfg
  57. README.md
  58. 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.

Optional - Full Build

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

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)