commit | 7d19ee9326fb55ac2c37083e5032d06f2c6d6b7b | [log] [tgz] |
---|---|---|
author | Shalom Gibly <sgibly@google.com> | Tue Jul 18 17:59:41 2023 -0700 |
committer | Shalom Gibly <sgibly@google.com> | Fri Aug 25 17:53:41 2023 -0700 |
tree | dae44a659135d7d012785d8d075a7f03c143ab2d | |
parent | 8b62951e065103a361d3e00d9c42b8235b5b4c41 [diff] |
Adds auto-mirroring support to the generated icons - Updated the vector XML parsing to read the `autoMirrored` attribute. - Generated a new `automirrored` package that holds auto-mirrored icons per icon-theme. For example: Icons.AutoMirrored.Filled.ArrowForward. - Updated the ImageVectorGenerator to generate and place auto-mirrored icons at the new package. - Have the generator mark any existing icons with an auto-mirrored version as deprecated, and suggest a replacement with the auto-mirrored one. - Updated the generated test files to include an additional property that have the ImageVectors with the auto-mirror flag. - Updated the tests to run against two groups of icons separately (mirrored and unmirrored). - Split the API files generation to icons.txt and automirroed_icons.txt. Update the icons.txt to hold only icons that are not in the automirrored_icons.txt file. Bug: 279989215 Test: Updated the generated test icons, and the tests themselves Relnote: "Added support for auto-mirrored icons when rendered in right-to-left layouts. Icons in the material-icons-core and material-icons-extended modules are now providing additional icon sets for supporting auto-mirroring when the icon allows it. The new sets are prefixed with `Icons.AutoMirrored.Filled...` etc., and hold icons that will auto-mirror on RTL layouts. See developers.google.com/fonts/docs/material_icons for the list of icons that can (and should) be auto-mirrored. The previously provided icon properties for those icons are now marked as deprecated, and provides a replacement-block suggestion to help with the migration. In case you don't have any special handling for mirroring icons on RTL, we recommend migrating to the new set of icons. For example, `Icons.Filled.ArrowBack` should be refactored to `Icons.AutoMirrored.Filled.ArrowBack`." Change-Id: I4b5116207cb9c0dd1a8a72d2bd3f606f8fdd0129
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.