I think examining other patterns would be useful.

This makes me think that the problem in the SO question you answered for me (posted under my old name) (https://stackoverflow.com/questions/76213875/fanning-out-and-summing-results-in-rxjs) could potentially be more efficiently handled with expand(). There are a couple of cases where I'm fetching all of a particular paginated resource using expand() and reduce(), but from what you've written here, I think I could use expand() to create an observable that emits each page of the resource data and chain further functions to operate on those pages.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

Aurelia Fenderson-Peters
Aurelia Fenderson-Peters

Written by Aurelia Fenderson-Peters

20+ years writing code of various sorts. Full of trans magic.

Responses (1)

Write a response

It worked! I think this is more efficient, because I'm not waiting to retrieve every page of a given resource before I build my counts.

--