Use of iterator_to_array in PaginatorAdapter for incorrect limit on dataset

[jeroenzwart]

We encountered the following problem in our application after v3.0. In de pagination after the update the number per page and the count per page is not matching anymore. When a request is made with an per page of 10, the response can be incorrect when using include in the request.

For example; the response in the request with per page of 10 returns a result of 10 hamburgers. When we also want in the same request the ingredients, the include 'ingredients' is provided. Just to explain, for convenience, each hamburger has 2 related ingredients. When the same request with include is executed, the result is 5 hamburgers with each 2 ingredients. The sum of 'all items' in the response is 10, which is incorrect.

When each hamburger has 3 ingredients, the result will be 3 hamburgers with 3 ingredients, plus 1 hamburger without any ingredients. The meta data of the pagination is incorrect. When the include param is deleted from the request, the number per page and the count of items stays the same.

---

In our app, before the update, when you made a call to and endpoint with an include the number of items per page was the what you got from as response, and according to the pagination: {{HOST}}/periods?include=closed&per_page=9

After the update the number per page and the count per page is not matching anymore.

When the include param is deleted from the request, the number per page and the count of items stays the same.

---

Based on the last code changes, I found that the change on this method broke the results. By reverting it to the use of iterator_to_array the number of results stays the same as the items per page.