Open apneadiving opened 3 years ago
Not all the results are returned immediately, and there may be more requests made behind the scenes as you iterate through the results. Calling anything that will force an iteration through all results will effectively exhaust the iterator. So if you want to process the results and also do one of these kinds of operations, you'll need to do both together in a single pass.
I don't think there's anything we could do to fix the behavior, but I will look at trying to update our documentation for the library to explicitly mention this.
I understand the ins and outs. Thank you
Using v6 of the api and the search service, using the same
search_query
andcustomer_id
in both scenari.I think the query is irrelevant here, the points are:
count
it seems to flush the resultsto_a
twice, it seems to flush the results