Way to fix this: TeamAtEventSummaryFragment needs to load the event info as well and add an observable combiner thing to create a composite data model of the Event and TeamAtEventStatus.
And then if the event comes back as unplayed, generate a placeholder item in TeamAtEventSummarySubscriber.
Currently, the subscriber just reads the event out of the local db, but if the event is unplayed, it never gets to this point. Instead, we can actually hit the API for the event (and that way it'll work better if the event happens to not be loaded) and use that result instead
This is a terrible experience.
Way to fix this:
TeamAtEventSummaryFragmentneeds to load the event info as well and add an observable combiner thing to create a composite data model of the Event and TeamAtEventStatus.And then if the event comes back as unplayed, generate a placeholder item in
TeamAtEventSummarySubscriber.Currently, the subscriber just reads the event out of the local db, but if the event is unplayed, it never gets to this point. Instead, we can actually hit the API for the event (and that way it'll work better if the event happens to not be loaded) and use that result instead
Existing code examples/references:
EventStatsFragmentTeamAtEventSummarySubscriber.isDataValidwill need to account for the unplayed event case, as will theparseDataimplementation