You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am thinking of introducing a major behavior breaking change when it comes to TabbedPages and deep linking.
Currently if you had the following link NavigateAsync("TabbedPage/SomeView") if "SomeView" was a tab, it would be selected and then navigation would continue. I am proposing to change this behavior to add a paremeter to indicate which tab you would like to select instead.
NavigateAsync("TabbedPage?selectedTab=SomeView")
In this case, the selected tab would be made using the parameter, and the SomeView would be created and added to the navigation stack using the standard deep link logic.
My only thought is how would we control nested navigation where your tab is a NavigationPage and you want to navigate in that tab only.
Currently done with: NavigateAsync("TabbedPage/NavigationPage/SomeView/SomeOtherView")
This would navigate to the tabbed page, selected the first NavigationPage it found, and then push the SomeOtherVew onto the stack.
I'm not sure I have an answer for that behavior at the moment.
This would also help address the issue of #650 and passing parameters to all tabs.
Thoughts?
The text was updated successfully, but these errors were encountered:
I am thinking of introducing a major behavior breaking change when it comes to TabbedPages and deep linking.
Currently if you had the following link
NavigateAsync("TabbedPage/SomeView")
if "SomeView" was a tab, it would be selected and then navigation would continue. I am proposing to change this behavior to add a paremeter to indicate which tab you would like to select instead.NavigateAsync("TabbedPage?selectedTab=SomeView")
In this case, the selected tab would be made using the parameter, and the SomeView would be created and added to the navigation stack using the standard deep link logic.
My only thought is how would we control nested navigation where your tab is a NavigationPage and you want to navigate in that tab only.
Currently done with:
NavigateAsync("TabbedPage/NavigationPage/SomeView/SomeOtherView")
This would navigate to the tabbed page, selected the first NavigationPage it found, and then push the SomeOtherVew onto the stack.
I'm not sure I have an answer for that behavior at the moment.
This would also help address the issue of #650 and passing parameters to all tabs.
Thoughts?
The text was updated successfully, but these errors were encountered: