commit | 6056a21a3cc02b241b46756d76788ff941e8f133 | [log] [tgz] |
---|---|---|
author | Agostinho Junior <junioraw@google.com> | Fri Jun 23 13:46:38 2023 +0000 |
committer | Agostinho Junior <junioraw@google.com> | Thu Jun 29 16:33:38 2023 +0000 |
tree | 4aac6a6c9235dbc4e7e9b89db60e12b7a5cb2085 | |
parent | c1188965414359d8ac7394ddce01068c426f99af [diff] |
Add request exercise route contract and expose exercise route. In more detail: 1. Create a new contracts package, which contains the new exercise route contract and a copy of the existing health permissions contract. 2. Add different subclasses for ExerciseRoute, depending on data and consent state. There are three possible states for the ExerciseRoute class: Data (for value returned in the record request), ConsentRequired (if the caller app doesn't yet have permission from the user to read the route), NoData (if there's no data to request permissions for). 3. Expose ExerciseRoute in the public API and the respective constructor of ExerciseSessionRecord that takes an ExerciseRoute. Contracts package is inspired by a pattern set by contracts in Jetpack (see known direct subclasses): https://developer.android.com/reference/androidx/activity/result/contract/ActivityResultContract Test: Added. Relnote: Added ExerciseRoute, ExerciseRoute.Data, ExerciseRoute.ConsentRequired and ExerciseRoute.NoData, exposed ExerciseRoute in the public API, added ExerciseRouteRequestContract, added HealthPermissionsRequestContract. Fix: 283450357 Fix: 286207148 Change-Id: Ief0e516cb08662c97cbee429bad1a3d284acb5b2
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.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
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.
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
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()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.