Open ccoffey opened 4 years ago
There's a lot of summary/detail situations in Strava API and for whatever reason I had chosen not to rebuild that hierarchy in this client. I would be open to refactoring that, possibly inheriting DetailedActivity
from SummaryActivity
or including it and delegating. Give it a shot.
This is easiest to explain by example:
My work around for this API weirdness is:
But I think it would be much clearer if
client.athlete_activities
returned[Strava::Models::SummaryActivity]
andclient.activity
returned aStrava::Models::DetailedActivity
.What do you think?