Optionally return an observable if no done method passed

for example:

clubs.get({myArgs}, function(err,payload){
    //do stuff
});

would still work but if no function is passed as the second argument an observable would be returned:

clubs.get({myArgs})
    .flatMap(returnedClubList => Rx.Observable.return(returnedClubList ))
    .flatMap(club => clubs.listMembers({getMembersFor: club}))
    .subscribe(clubMember => console.log("club member: " + clubMember);

this would return a list of all club members from all clubs returned from the initial call.

Would you accept a pull request for this?

[TimoStaudinger]

I really like the idea, as this results in a much nicer API in my opinion.

Any reason you would use observables rather than promises? I would argue that promises are the better choice here, as they also seem to cover all use cases, do not introduce an additional dependency to ReactiveX and keep the libray’s API in line with the fetch() API etc:

const flatten = arr => arr.reduce((acc, cur) => acc.concat(cur), [])
strava.clubs.get({myArgs})
    .then(clubs => clubs.map(club => strava.clubs.listMembers(club)))
    .then(flatten)
    .then(members => members.forEach(m => console.log('club member:', m)));

[markstos]

Observables won’t be implemented, but my Promise-based PR will be merged and released now that I’m maintainer. Closing this.