Getting status of instances does not support continuation token

[przemos]

It seems that as much as C# version of the library supports continuation token while iterating over execution instances with History API, NodeJS does not. Instead, it tries to encapsulate iteration process by managing continuation token itself.
Unfortunately, as much as some people may consider it useful, in general, it is quite limiting. It is limiting for wrong reasons - it would be nice to keep the API on par with C# one as much as possible for consistency.

Imagine you have 100K executions. Do you really want to fill up your process' memory with 100K rows or let the user decide how the paging over will be implemented e.g. read 1000 rows, process them, dispose, then another 1000 rows, etc. ?

[davidmrdavid]

Thanks for the feature request, @przemos. Broadly speaking, I agree that we want to keep the NodeJS SDK as feature-complete as possible, as I'm doing some work behind the scenes to help us do that here and across the other Durable SDKs. I can't speak much about that publically at the moment, but I figured I'd hint at it since you mentioned that we want to keep the API on par with C# - which is one of our goals!

This does need some design though. Could you provide us with a few sample code snippets to exemplify what programming experience you'd expect for this feature? More concretely, what's an example syntax you'd use to manage the pagination logic as part of your user code. We can use that as a starting point for the design here. Thanks!