v1.1.14

Fixes for VerifyNavigation when using the Uri based api's.

As reported in #11 when attempting to verify the following navigation:

navigationService.VerifyNavigation(x => x.NavigateAsync("/RootPage/WelcomeTutorialPage"), Times.Once);

The actual path provided to prism would not be verified, however if your expected uri was:

navigationService.VerifyNavigation(x => x.NavigateAsync("http://localhost/RootPage/WelcomeTutorialPage"), Times.Once);

The expression would be satisfied and work.

The cause of this has been identified as a faulty assumption made about the use of extension methods internally in the library. Now these are properly inspected to ensure we grab the correct argument to compare the navigation against. Many thanks to @ MiloszKowalski for providing a very detailed issue breaking down exactly what was causing this issue and making it so easy to provide a fix!

What's Changed

• Fixed Uri Navigation Verifications by @Axemasta in #13
• This build no longer has a dependency on maui, Originally I believe this might be necessary however removing the maui references has not affected the behaviour of the library so thats one less dependency to worry about!

Full Changelog: v1.1.2...1.1.14