commit | 867de855afa51458fa8bdb529894da6b6d5822b3 | [log] [tgz] |
---|---|---|
author | Jeremy Woods <jbwoods@google.com> | Wed Aug 17 16:42:52 2022 -0700 |
committer | Jeremy Woods <jbwoods@google.com> | Tue Aug 23 14:49:08 2022 -0700 |
tree | 1f5f39ffb20ea70f9b195450a70d0cfe3ce7077c | |
parent | 16e76b7dde6ab511fe86ac81927cc999bd312ae5 [diff] |
Fix Navigator singleTop When doing onLaunchSingleTop the Navigator currently calls the navigate function that takes a destination, which only the Navigator actually implements. We should instead be using the navigate call that takes NavBackStackEntries which all the extended Navigators also implement, which will ensure they are called even if they don't already explicitly handle single top. RelNote: "Navigation will now properly replace the Fragment instance when navigating to the same destination and setting the `launchSingleTop` flag to true." Test: Added NavControllerWithFragmentTest Bug: 237374580 Change-Id: I5a2f15e1c2a9a4bc5bae6f5d016a9b06b76aa448
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.