Bump Prism.Wpf from 6.3.0 to 7.2.0.1367

[dependabot-preview]

Bumps Prism.Wpf from 6.3.0 to 7.2.0.1367.

Release notes

Sourced from Prism.Wpf's releases.

7.2.0.1367

Summary

Prism 7.2 represents some major fundamental changes. Be sure to read the release notes in full. In addition to adding several new great API's there are some major breaking changes particularly for Xamarin.Forms developers.

Prism.Core

• #1668: Expands IoC abstractions to allow checking for registered services and naming instances or singletons.
• #1680: Fixes Ambiguous match when using DelegateCommand.ObserveProperty
• #1677: Changes IContainerRegistry to provide a Fluent API
• #1796: Optimize Weak DelegateReference for EventAggregator

Prism.Forms

• #1589: OnNavigatedFrom method is not called when changing detail on MasterDetailPage
• #1615: Add the ability to switch tabs
• #1625: Master Detail to Tab Page Navigation broken in 7.1
• #1683: Add navigation animation or modal navigation with XAML Navigation Extensions
• #1663: Refactored platform navigation methods
• #1669: Allow Create/Destroy Action Sheet buttons with only a name. Allow passing tuples to Navigation Service
• #1700: Platform Specific View Registration not respected
• #1704: Make XAML Navigation Extensions inherit from BindableObject. Make properties Bindable
• #1748: [BREAKING] Make INavigatingAware Obsolete and introduce IInitialize, IInitializeAsync & IAutoInitialize
• #1754: Fully support bindings for XAML Navigation
• #1757: Add Automatic View Registration
• #1806: Removes FastExpressionCompiler for DryIoc due to iOS incompatibility
• #1814: Adding DialogService
• #1822: Enhancing Modal Logic to reduce/eliminate need to specify modal navigation when Navigating Back. Enhances Navigation Exception Messaging with new NavigationException class
• #1842: Fixes reparenting bug for DialogService in XF 4.X on Android with Screen Reader enabled

View/ViewModel Initialization

After numerous user survey's and interviews it became apparent that the intent of INavigatingAware had been become unclear and that users were actually overwhelmingly asking for a breaking change. INavigatingAware is no longer supported. For those who may be using OnNavigatingTo with INavigationAware this will be most impactful as a behavior change as INavigatingAware has been removed from INavigationAware meaning that it will no longer be called. For those who have implemented INavigatingAware directly you will see a build error. The impact should be minimal by simply renaming all instances of INavigatingAware to Initialize.

Using IAutoInitialize

IAutoInitialize is designed for those cases where you are passing objects around. By default we do a Non-Case-Sensitive lookup between the Navigation|Dialog Parameters and the Properties in your ViewModel. If one is found we will automatically try to set the property for you.

_navigationService.NavigateAsync("ViewB" ("title", "Hello World"), ("fooBar", "some other value"));

public class ViewBViewModel : IAutoInitialize
{
    public string Title { get; set; }
    public string FooBar { get; set; }
}

In the above example your ViewModel will be initialized with the values passed in the NavigationParameters or DialogParameters. If these are static variables (meaning the won't change during the lifecycle of your View/ViewModel you would not need to implement INotifyPropertyChanged for them.

... (truncated)

Commits

• 128328a release script in yml - script shouldn't be published
• c8a9f8b fixing script path
• ae8135a move ps script to ps1
• 8611a0f fix artifact path
• 6bd9c47 update funding
• cacf992 add funding
• 21b5bac Merge pull request #1846 from Thieum/patch-1
• 25f09c8 typo
• 5dbd2e2 Merge pull request #1843 from andreinitescu/PartialViewsImprovements
• b200a01 Merge pull request #1842 from PrismLibrary/dialogupdates
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[dependabot-preview]

Superseded by #12.