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
We have two struct types, Show and ShowMeta. Of these, ShowMeta actually represents a show (and other places eg. the website internally call this thing a show). Show seems to be a mix of things relating to timeslots and things relating to shows.
I was quite confused by this---is there anything better we can call Show so ShowMeta can be named Show? Why does Show (the existing one) exist in the first place---ideally it shouldn't be needed as timeslots should cover this information, is this a MyRadio problem?
The text was updated successfully, but these errors were encountered:
I believe this was my bad, when I was writing these additional structs I didn't really understand what they actually represented 😝 I believe we should refactor to bring it inline with the api, so Show, Season, Timeslot, etc.
We have two struct types,
Show
andShowMeta
. Of these,ShowMeta
actually represents a show (and other places eg. the website internally call this thing a show).Show
seems to be a mix of things relating to timeslots and things relating to shows.I was quite confused by this---is there anything better we can call
Show
soShowMeta
can be namedShow
? Why doesShow
(the existing one) exist in the first place---ideally it shouldn't be needed as timeslots should cover this information, is this a MyRadio problem?The text was updated successfully, but these errors were encountered: