APIClient::item_iterator: reset query_parameters after returning all items#23
Merged
ricardofontanelli merged 1 commit intomasterfrom Oct 26, 2022
Conversation
adf106f to
9c174a3
Compare
9c174a3 to
1517b4d
Compare
…items The item_iterator method uses a query parameter called `since` to get the next results from the API resource when the previous response includes a hasMore=True property. The problem here is the last API call leaves the query parameter defined to a value related to the previous resource retrieved, and if you use the same api client to iterate over different resources (i.e. campaigns), the results will always be affected by the previous call.
1517b4d to
d8ff5eb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The item_iterator method uses a query parameter called
sinceto get the next results from the API resource when the previous response includes a hasMore=True property.The problem here is the last API call leaves the query parameter defined to a value related to the previous resource retrieved, and if you use the same api client to iterate over different resources (i.e. campaigns), the results will always be affected by the previous call.
In the case below, since the
apivariable is defined outside the loop (as expected), responses for campaign22222will be affected by thesinceproperty from the last call to campaign11111resulting in fewer responses or, in many cases, empty result.Example:
It's probably the same issue reported here.