You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For processing paged results we have very helpful function called process. Currently it's default setting for accumulate results is true which depending on amount of pages and data callback function produces, might lead to unpredictable memory consumption. Because of that on every usage we have to explicitly override defaults with process(myCallbackFn, { accumulate: false }).
While this a good step forward, this is a breaking change. And I have mixed feelings about breaking the SDK in this manner. I will however support it in the JS SDK
Description
For processing paged results we have very helpful function called
process
. Currently it's default setting foraccumulate
results istrue
which depending on amount of pages and data callback function produces, might lead to unpredictable memory consumption. Because of that on every usage we have to explicitly override defaults withprocess(myCallbackFn, { accumulate: false })
.Expected Behavior
Default for accumulate should be
false
Current Behavior
Default for accumulate is
true
The text was updated successfully, but these errors were encountered: