This should be a simple MVVM - reactive architecture question, something that I miss probably.
I'll start with a context example:
I have a Music Tracks Player application with 2 models Player and Track. The relation between player and track is pretty obvious: the player contains tracks (multiple track can be played simultaneously), so in an Object Orient architecture I would store (or reference I should say) a list of tracks objects inside a player instance.
How should I reflect this relation On my MVVM reactive app? should I create player model that holds a list of tracks? or should I have handle them separately on my View-Model? If I store only the Player model then how do I detect changes on each Track (for example progress of a track)? Or maybe each View part (Player, and list of tracks) should have its own view-model, but then how would they know about each other for example a player need to know how much tracks it has for some logic calculations for view representation?
On my View side I have to show both of them, for example the player state (name, status, metadata) and for every track I should display the current position in track etc.