commit | 0069c4a1d39946265dbe019017d3932a8f2d72ed | [log] [tgz] |
---|---|---|
author | Charles Chen <[email protected]> | Fri Nov 04 15:07:26 2022 +0800 |
committer | Charles Chen <[email protected]> | Fri Dec 02 15:52:23 2022 +0800 |
tree | a0be248b676574f35ec5e074e150f1a1d43ac81a | |
parent | 85b108a7837679e9378e9185411a144fb074b83d [diff] |
Address ActivityEmbedding APIs feedback 1. Add descriptions on layoutDirection 2. See below Relnote RelNote: " 1. Align the API naming - Use add/remove for multiple instances: - registerRule changes to addRule - unregisterRule changes to removeRule 2. Replace getSplitRules with getRules since ActivityRule is not a split rule 3. Add RuleController#setRules to set a bunch of rules 4. Extract rule related APIs from SplitController to singleton RuleController. They are: - addRule - removeRule - getRules - setRules - clearRules - parseRules 5. Extract #isActivityEmbedded from SplitController to singleton ActivityEmbeddingController. They are: - isActivityEmbedded 6. Remove SplitController#initialize. To set rules from XML file, please use RuleController#parseRules and #setRules. Before this change: SplitController.initialize(context, R.xml.static_rules) After this change: val ruleController = RuleController.getInstance(context) val rules = ruleController.parseRules(R.xml.static_rules) ruleController.setRules(rules) 7. We don't distinguish static rules with runtime rules anymore. That said, calling #clearRules results to clear all rules no matter they are registered with static XML rule definitions or at runtime. To have the legacy behavior of `SplitController#clearRegisteredRules`, please call `RuleController#parseRules` with the XML resources id and call `RuleController#setRules` to set back the rules again. Before this change: SplitController.getInstance(context).clearRegisteredRules() After this change: val ruleController = RuleController.getInstance(context) val rules = ruleController.parseRules(R.xml.static_rules) ruleController.setRules(rules) " Test: presubmit Bug: 255952916 Merged-In: Ib39671fb22a9ccef3b0aa8967ee18c3168c54c63 Change-Id: Ib39671fb22a9ccef3b0aa8967ee18c3168c54c63
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()
, jcenter()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.