Fixed
Status Update
Comments
fr...@ingenie.com <fr...@ingenie.com> #2
I would also like to see this.
In my multi-module project, I am unable to find a way to animate between modules, without an animation which shows the whole activity being replaced - even if the only change needed is a fragment transition.
In my multi-module project, I am unable to find a way to animate between modules, without an animation which shows the whole activity being replaced - even if the only change needed is a fragment transition.
il...@google.com <il...@google.com> #3
Re #2 - please file a separate bug for your animation issue with a sample project that reproduces the issue.
[Deleted User] <[Deleted User]> #4
We do use uri base navigation within our application very often and this is a blocker for us to upgrade to the latest RC as onHandleDeepLink used to not clear the backstack. I would appreciate if this can get into the v1 or if not soon after.
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #5
Project: platform/frameworks/support
Branch: androidx-master-dev
commit ffcb91a4f35e0221b0bb3fb4b6b44d1a77bc9f7b
Author: jbwoods <jbwoods@google.com>
Date: Tue Apr 09 13:53:57 2019
Allow navigating in app via deep link URIs
Adds API to call navigate() with a deeplink. It also allows for navigation
to destinations within other graphs (as long as the graphs are included
together by higher level modules). A new destination is added to the back
stack and popping it returns to the previous destination, even if it is
in a different graph.
Test: new tests and ran nav controller tests
./gradlew checkApi
BUG: 110412864
Change-Id: Ie88f3ab8359c6a9fde28f0fc29c1917cc23f41f7
M navigation/runtime/api/2.1.0-alpha03.txt
M navigation/runtime/api/current.txt
M navigation/runtime/src/androidTest/java/androidx/navigation/NavControllerTest.kt
A navigation/runtime/src/androidTest/res/navigation/nav_multiple_navigation.xml
M navigation/runtime/src/main/java/androidx/navigation/NavController.java
https://android-review.googlesource.com/941801
https://goto.google.com/android-sha1/ffcb91a4f35e0221b0bb3fb4b6b44d1a77bc9f7b
Branch: androidx-master-dev
commit ffcb91a4f35e0221b0bb3fb4b6b44d1a77bc9f7b
Author: jbwoods <jbwoods@google.com>
Date: Tue Apr 09 13:53:57 2019
Allow navigating in app via deep link URIs
Adds API to call navigate() with a deeplink. It also allows for navigation
to destinations within other graphs (as long as the graphs are included
together by higher level modules). A new destination is added to the back
stack and popping it returns to the previous destination, even if it is
in a different graph.
Test: new tests and ran nav controller tests
./gradlew checkApi
BUG: 110412864
Change-Id: Ie88f3ab8359c6a9fde28f0fc29c1917cc23f41f7
M navigation/runtime/api/2.1.0-alpha03.txt
M navigation/runtime/api/current.txt
M navigation/runtime/src/androidTest/java/androidx/navigation/NavControllerTest.kt
A navigation/runtime/src/androidTest/res/navigation/nav_multiple_navigation.xml
M navigation/runtime/src/main/java/androidx/navigation/NavController.java
ap...@google.com <ap...@google.com> #6
Project: platform/frameworks/support
Branch: androidx-master-dev
commit d967abdf673a9ab9249fedead4cb0389139e7e70
Author: jbwoods <jbwoods@google.com>
Date: Thu Apr 18 15:36:48 2019
Add hasDeepLink Api to NavDestination
When users attempt to navigate to a deep link destination, if the deep
link is invalid an IllegalArgumentException is thrown. This Api offers
a way to verify the deeplink is valid before attempting to navigate, and
gives developers more flexibility to handle the case where the deep link
may be invalid.
It uses matchDeepLink() and returns whether a match was found.
Test: New tests and ./gradlew checkApi
BUG: 117437718, 110412864
Change-Id: Iabbca9cfbb864ce305d84d9e4f616d2b43dc7ac6
M navigation/common/api/2.1.0-alpha03.txt
M navigation/common/api/current.txt
M navigation/common/src/androidTest/java/androidx/navigation/NavDestinationAndroidTest.kt
M navigation/common/src/main/java/androidx/navigation/NavDestination.java
M navigation/runtime/src/main/java/androidx/navigation/NavController.java
https://android-review.googlesource.com/948136
https://goto.google.com/android-sha1/d967abdf673a9ab9249fedead4cb0389139e7e70
Branch: androidx-master-dev
commit d967abdf673a9ab9249fedead4cb0389139e7e70
Author: jbwoods <jbwoods@google.com>
Date: Thu Apr 18 15:36:48 2019
Add hasDeepLink Api to NavDestination
When users attempt to navigate to a deep link destination, if the deep
link is invalid an IllegalArgumentException is thrown. This Api offers
a way to verify the deeplink is valid before attempting to navigate, and
gives developers more flexibility to handle the case where the deep link
may be invalid.
It uses matchDeepLink() and returns whether a match was found.
Test: New tests and ./gradlew checkApi
BUG: 117437718, 110412864
Change-Id: Iabbca9cfbb864ce305d84d9e4f616d2b43dc7ac6
M navigation/common/api/2.1.0-alpha03.txt
M navigation/common/api/current.txt
M navigation/common/src/androidTest/java/androidx/navigation/NavDestinationAndroidTest.kt
M navigation/common/src/main/java/androidx/navigation/NavDestination.java
M navigation/runtime/src/main/java/androidx/navigation/NavController.java
il...@google.com <il...@google.com> #7
This has been implemented internally and will be available in Navigation 2.1.0-alpha03.
Now in addition to navigating via an R.id, you can reuse the same <deepLink> elements in your graph to navigate(Uri).
Now in addition to navigating via an R.id, you can reuse the same <deepLink> elements in your graph to navigate(Uri).
Description
Version used: 1.0.0-alpha02
Navigating via id works great for flat navigation graphs contained within a single module, but for multi-module cases that have separate graphs (included together by higher level modules), there's no easy way to navigate bidirectionally between them.
It would be nice to be able to navigate via URI, preferably in a way that would allow you to navigate to destinations even within other graphs (which normally you wouldn't be able to navigate directly to).
This would differ from using NavDeepLinkBuilder since it wouldn't blow away the back stack with a synthetic back stack, but just add the new destination to the back stack just like any other navigate() call.