From be3564034fa4c33b67d79861ed5bd322148c0e4b Mon Sep 17 00:00:00 2001 From: Andres Pineda <1900897+ajpinedam@users.noreply.github.com> Date: Wed, 25 Sep 2024 15:53:48 -0400 Subject: [PATCH] chore: apply suggestions from code review Co-authored-by: Xiaotian Gu --- doc/reactive-migration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/reactive-migration.md b/doc/reactive-migration.md index 21cc1e7f9..9a5572da8 100644 --- a/doc/reactive-migration.md +++ b/doc/reactive-migration.md @@ -10,9 +10,9 @@ Upgrading to Uno.Extension.Reactive V5 should not require any changes to your ap ### MVUX Generated Code -As of V4, the MVUX analyzer generated a bindable proxy for each of the models in your app. For example, the bindable proxy for `MainModel` was named `BindableMainModel`. +In V4, the MVUX analyzer generates a bindable proxy for each of the models in your app. For example, the bindable proxy for `MainModel` was named `BindableMainModel`. -This behavior changed in V5, and the MVUX analyzer will now generate a ViewModel class for each of your app's models. For example, the generated code for `MainModel` is named `MainViewModel`. +This behavior has changed in V5, and the MVUX analyzer will now generate a ViewModel class for each of your app's models. For example, the generated code for `MainModel` will be named `MainViewModel`. > [!IMPORTANT] > You don't have to do anything if you update but want to keep the old behavior. The generator will continue to generate the bindable proxies.