UniRx VS Dynamic Data

Personally I use UniRx, but there's plenty of flavours of event systems to dig into.

What paradigms & design patterns that those of you whom have more experience than I recommend? I've been advised to use things Dependency Injection (Extenject) and/or Reactive programming (UniRx), but that came from someone whose background isn't Unity. I would like to do this right the first time and make the code as maintainable as possible; we will be using it again in the future.

This is pretty cool. I wrote something similar for a narrower problem space: RolePlay Attributes. UniRx’s Reactive Properties feel like the total package but with a conceptual and dependency overhead.

Interesting, I hadn't heard of UniTask. I use UniRX in my projects which I think solves similar problems in a bit of a different way.

Sure, knowing the patterns and instead of using first order language features, you may get your own implementation of "observer" or something alike. But if you see your system becomes "event-heavy" it's maybe time to think about getting already complete solution: https://github.com/neuecc/UniRx // how to MV(R)P

The reason I'm leading things in this direction is because I highly recommend picking up UniRx. It brings reactive programming into your game development workflow and will completely change the way you look at development.

You should take a look at https://github.com/neuecc/UniRx, it allows you to subscribe to IObsevables. What I do is all my data objects use Properties that are observeable, which allows me for example to bind an object to the UI once, which then changes depending on the data state.

You can use Observables: https://github.com/neuecc/UniRx

In the realm of .NET development, managing collections and their changes can be a challenging task, especially in applications with complex data flows and user interfaces. This is where DynamicData, a library in the .NET ecosystem, comes into play. It simplifies reactive data management, making it easier for developers to handle complex data operations with ease. This article aims to provide a comprehensive understanding of DynamicData, its core concepts, and practical applications.

Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.

With DynamicData you can use a ObservableCollectionExtended for your list and call .ToObservableChangeSet().WhenAnyPropertyChanged().Subscribe(t => { code to execute });

reminds a lot of https://github.com/reactivemarbles/DynamicData

If you're trying to use reactive with MVVM, you might have a look at ReactiveUI, an MVVM toolkit designed to work with reactive extensions. Specifically in this case, you could leverage DynamicData (RXUI's preferred method of handling collections), which lets you trigger updates based on change notification from child items, among other things. I'm still relatively new to RXUI myself, but if you have any questions I can certainly try to help a bit more.

Right and I never said they did. I said replace the observablecollection with an iobservable if you want it to be observable. You can then use https://github.com/reactivemarbles/DynamicData to get yourself an observablecollection. I'm not arguing that observablecollection + linq would result in an observablecollection. Just pointing out that there is a solution for this.