I've been spinning my wheels looking at ReactiveUI, ReactiveUI.Fody, ReactiveUI.SourceGenerator and even Fody/PropertyChanged.Fody.

I cannot for the life of me figure out how to get it implemented. I've trying to find videos, combing through every piece of documentation onhttps://www.reactiveui.net/ or any question concerning those packages on StackOverflow. The documentation is extensive but also leave a lot of questions unanswered.

https://www.reactiveui.net/docs/getting-started/installation/blazor.html states:

InstallReactiveUI into your netstandard libraries and tests.
InstallReactiveUI.Blazor into your application.
InstallReactiveMarbles.ObservableEvents.SourceGenerator into your application.
InstallReactiveUI.Testing into your tests.

But then I never see mention of ReactiveMarbles.ObservableEvents.SourceGenerator again.

I've been tohttps://github.com/reactiveui/ReactiveUI.Samples/tree/main/blazor
But the server sample is only using ReactiveUI.Blazor but then includes FodyWeavers.xml.

Please help me understand how this all works. I've hit a total wall at this point and have spent several day now trying to figure out how this all connects.

This is my goal:

My Class flow is

(MainModel => FirstCollection) =>
(SecondModel => NestedProperty) =>
(ThirdModel => NestedProperty) =>
(FourthModel => SecondCollection) =>
(FithModel (Constains a bunch of properties and is the last model in the chain)

When any property of FithModel change, MainModel needs to be notified. Basically if there is any change, to any property anywhere in MainModel, MainModel should be notified. I then have a razor page with and EditContext that is watching MainModel. When MainModel detects that change,EditContext.OnFieldChanged should be triggered.

Essentially when anything in MainModel changes I just want it to say "Hey! I changed!" I dont care what the actual value or what property changed, just that something changed.

My use-case:
We have a form which initially prepopulates via an existing record in our database. You have the ability to make form selection changes before generating a report. What happens currently, is that after a report has been generated (which creates a clickable report link in the form of a button) you can then go make a change to a form selection and then could accidently look at the previous report. I need to know every time any form selection changes, so I can clear out that link forcing the user to regenerate the report, creating a new report link.

It should be noted that this is an application that I inherited and thus had no input on the application architecture.

The goal is to have as minimal boilerpate code for change detection.

Thank you for your help! ❤️