fix(pageIterator): stop mutating PageCollection #961
Merged
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.
A similar PR may already be submitted! Please search among the Pull request before creating one.
Thanks for submitting a pull request! Please provide enough information so that others can review your pull request.
NOTE: PR's will be accepted only in case of appropriate information is provided below
Summary
PageIterator is mutating the pageCollection he receive in his constructor when it iterates.
The pageCollection.value array will be empty after the call of the iterate method.
The iterate method should not mutate pageCollection.value.
(cfr: #959)
Motivation
Mutation of given parameter is always a bad things and lead application to unexpected behaviour.
Test plan
Demonstrate the code is solid. Example: The exact commands you ran and their output.
I haded an unit test is the PR.
Closing issues
Fixes #959
Types of changes
Checklist