Implement NavigateFromAsync method without recreating a page.

[niimima]

Description of Change

Adding NavigateFromAsync methods without recreating a page.

Bugs Fixed

• fixes [Enhancement] NavigateFrom #3118

API Changes

List all API changes here (or just put None),

Added:

• Task INavigationService.NavigateFromAsync(string viewName, Uri route, INavigationParameters parameters);
• Task INavigationServiceExtensions.NavigateFromAsync(this INavigationService navigationService, string viewName, Uri route)

Behavioral Changes

No changes. Only additions of features.

PR Checklist

• Has tests (if omitted, state reason in description)
• Rebased on top of master at time of PR
• Changes adhere to coding standard

[niimima]

I have a concern regarding the pull request I've created. When searching for a page using viewName, if it is not found, what would be the recommended behavior?
https://github.com/PrismLibrary/Prism/pull/3182/files#diff-8ae9340c7f10510f59a045175866a15bdb8ed35b541c8256cf73252dafadc343R350-R356

In the current implementation, pages specified by route appears directly under the window.

[AmrAlSayed0]

Parent page? Shouldn't this be the page before the current page in the stack and if it is the root page then we get the parent page?

[brianlagunas]

@AmrAlSayed0 is correct. While we do care about the parent in some scenarios, what we really need is the previous page in the navigation stack.

[niimima]

There are still some issues remaining, but I have made corrections to use the NavigationStack as described in the following link.

Prism/src/Maui/Prism.Maui/Navigation/PageNavigationService.cs

Lines 351 to 383 in 7f8a12f

	// Find a page that matches the viewName.
	var currentPage = GetCurrentPage();
	var navigationPages = currentPage.Navigation.NavigationStack.ToList();
	navigationPages.Reverse();
	var foundPage = navigationPages.FirstOrDefault(page => ViewModelLocator.GetNavigationName(page) == viewName);
	if (foundPage is null)
	{
	// Find a page from parents.
	var page = currentPage;
	while (page != null)
	{
	if (page is not null && ViewModelLocator.GetNavigationName(page) == viewName)
	break;
	page = page.GetParentPage();
	}
	currentPage = page;
	}
	else
	{
	// Insert RemovePageSegment.
	var removePageCount = navigationPages.IndexOf(foundPage);
	var tempQueue = new Queue<string>();
	for (int i = 0; i < removePageCount; i++)
	{
	tempQueue.Enqueue(RemovePageSegment);
	}
	while(navigationSegments.Count > 0)
	{
	tempQueue.Enqueue(navigationSegments.Dequeue());
	}
	navigationSegments = tempQueue;
	}

[brianlagunas]

This PR is not performing the actions required of the issue. Per the issue

This API should then effectively do the same as ../../SomePage where the ../.. is replaced by going back until we found the View that was specified.

This means you must first find the page, while keeping track of the number of times we must navigate back until we reach this page, and then begin navigating forward from there.

Decisions must also be made as to whether this can be supported in both a modal and non-modal navigation stack. While also considering the page's parent such as a TabbedPage or FlyoutPage

[niimima]

@brianlagunas

This PR is not performing the actions required of the issue. Per the issue

This API should then effectively do the same as ../../SomePage where the ../.. is replaced by going back until we found the View that was specified.

This means you must first find the page, while keeping track of the number of times we must navigate back until we reach this page, and then begin navigating forward from there.

Decisions must also be made as to whether this can be supported in both a modal and non-modal navigation stack. While also considering the page's parent such as a TabbedPage or FlyoutPage

Thank you for your feedback. Firstly, I am working on ensuring that the navigation works correctly with both TabbedPage and FlyoutPage. The FlyoutPage seems to be working well, but I need to confirm the specifications for the TabbedPage.

In the existing NavigateAsync method, you can use KnownNavigationParameters to either create or select a tab. For the NavigateFromAsync method, which approach would be more appropriate? Or, would it be better to dynamically switch between creating and selecting tabs based on the situation?

[dansiegel]

This really should work across both Modal and Non-Modal Navigation Stacks. I would suggest looking at the helpers we have that walk the NavigationStack today. That should help you to build something that can go the reverse direction to locate a given view.

[dansiegel]

This would need some overloads that take a string for the route as well.

[dansiegel]

Suggested change

	if (route.IsAbsoluteUri) throw new NavigationException(NavigationException.UnsupportedAbsoluteUri);
	if (route.IsAbsoluteUri)
	throw new NavigationException(NavigationException.UnsupportedAbsoluteUri);

[dansiegel]

Suggested change

	public const string UnsupportedAbsoluteUri = "An unsupported absolute uri. Please use a relative URI.";
	public const string UnsupportedAbsoluteUri = "Absolute Uri's are not supported when Navigated from a named source View. Please use a relative Uri.";