Added more notes on the breaking changes

Author: Sergio0694

CHANGELOG.md

@@ -6,37 +6,20 @@
 
 🆕 Added a new `WeakReferenceMessenger` type. This type is less performant than the other messenger, and uses more memory, and in return only uses weak references to track recipients. This type essentially mirrors the behavior of the `Messenger` type from `MvvmLight`, making the transition easier for developers migrating from that library.
 
-🆕 Introduced a new custom delegate to represent message handlers, which also receives the current recipient as additional input parameter (see code changes below).
+🆕 Introduced a new custom delegate to represent message handlers, which also receives the current recipient as additional input parameter (💥 breaking change, see code changes below).
 
-✅ Renamed `Messenger` to `StrongReferenceMessenger`.
+✅ Renamed `Messenger` to `StrongReferenceMessenger` (💥).
 
-✅ The `WeakReferenceMessenger` is now the default messenger used by the `ObservableRecipient` class.
+✅ The `WeakReferenceMessenger` is now the default messenger used by the `ObservableRecipient` class (💥).
 
-✅ Changed `ObservableObject` overloads using `Expression<Func<T>>` to be more efficient (see code changes below).
+✅ Changed `ObservableObject` overloads using `Expression<Func<T>>` to be more efficient (💥).
 
-✅ API changes to the `SetPropertyAndNotifyOnCompletion` (as detailed in [this blog post]( https://devblogs.microsoft.com/pax-windows/mvvm-toolkit-preview-3-the-journey-of-an-api/)).
+✅ API changes to the `SetPropertyAndNotifyOnCompletion` (as detailed in [this blog post]( https://devblogs.microsoft.com/pax-windows/mvvm-toolkit-preview-3-the-journey-of-an-api/), 💥).
 
-🚨 Removed the `Ioc` class (we will include docs on how to easily start using the `Microsoft.Extensions.DependencyInjection` library directly to work with dependency injection).
+🚨 Removed the `Ioc` class (we will include docs on how to easily start using the `Microsoft.Extensions.DependencyInjection` library directly to work with dependency injection, 💥).
 
 ## Breaking changes
 
-💥 If you were using the `ObservableObject.SetProperty<T>(Expression<Func<T>>, ...)` overload, the code needs to be updated as follows to replace the LINQ expression with a stateless lambda expression:
-
-```cs
-private readonly User user;
-
-public string Name
-{
-    // Preview 2
-    set => SetProperty(() => user.Name, value);
-
-    // Preview 3
-    set => SetProperty(user.Name, value, user, (u, n) => u.Name = n);
-}
-```
-
-The syntax is slightly more complex, but results in a 150x speed improvement (that's not a typo), requires no memory allocations at all and no reflection, and ensures that all necessary validation of the arguments can be done at compile time too.
-
 💥 If you were registering message handlers, no API changes are required for messages registered through the `IRecipient<TMessage>` interface. If you were manually registering handlers with the `Action<TMessage>` delegate instead, you will need to modify their code as follows:
 
 ```cs
@@ -67,6 +50,47 @@ Messenger.Register<MyViewModel, MyMessage>(this, (recipient, message) =>
 
 💥 If you want to use the `StrongReferenceMessenger` class for better performance, make sure to pass that to the constructor of the `ObservableRecipient` class, otherwise the `WeakReferenceMessenger.Default` instance will be used.
 
+💥 If you were using the `ObservableObject.SetProperty<T>(Expression<Func<T>>, ...)` overload, the code needs to be updated as follows to replace the LINQ expression with a stateless lambda expression:
+
+```cs
+private readonly User user;
+
+public string Name
+{
+    // Preview 2
+    set => SetProperty(() => user.Name, value);
+
+    // Preview 3
+    set => SetProperty(user.Name, value, user, (u, n) => u.Name = n);
+}
+```
+
+The syntax is slightly more complex, but results in a 150x speed improvement (that's not a typo), requires no memory allocations at all and no reflection, and ensures that all necessary validation of the arguments can be done at compile time too.
+
+💥 If you were using `SetPropertyAndNotifyOnCompletion`, change the code as follows:
+
+```csharp
+// Preview 2
+private Task<string> myTask;
+
+public Task<string> MyTask
+{
+     get => myTask;
+     set => SetPropertyAndNotifyOnCompletion(ref myTask, () => myTask, value);
+}
+
+// Preview 3
+private TaskNotifier<string> myTask;
+
+public Task<string> MyTask
+{
+    get => myTask;
+    set => SetPropertyAndNotifyOnCompletion(ref myTask, value);
+}
+```
+
+💥 If you were using the `Ioc` class, we will provide docs to illustrate how to setup a custom service container using the `Microsoft.Extensions.DependencyInjection` library soon. The temporary link with the preview docs for this is available [here](https://github.com/windows-toolkit/MVVM-Samples/blob/feature/preview2-update/docs/mvvm/Ioc.md).
+
 ## Notes
 
 For additional info and discussion, see the related issue [here](https://github.com/windows-toolkit/WindowsCommunityToolkit/issues/3428).