You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the design of all the method calls coming off the data objects you do not need to access the parent object that created it 90% of the time but i am finding for example that sometime when working at the episode level i need some info from the server or library or account. One option is to just pass those other objects around and that is how i work around it but i beleive a lot of those objects or their info are already in these child objects so it could maybe be exposed.
I work around it anyway so if it is too hard don't worry it was just an idea.
This would be an enhancement not a bug
The text was updated successfully, but these errors were encountered:
With the design of all the method calls coming off the data objects you do not need to access the parent object that created it 90% of the time but i am finding for example that sometime when working at the episode level i need some info from the server or library or account. One option is to just pass those other objects around and that is how i work around it but i beleive a lot of those objects or their info are already in these child objects so it could maybe be exposed.
I work around it anyway so if it is too hard don't worry it was just an idea.
This would be an enhancement not a bug
The text was updated successfully, but these errors were encountered: