[Nyholm]

The AbstractApi::setPerPage() was removed in the 3.0. I cannot find what PR that removed it.

However, we kept AbstractApi::$perPage and we do use it on a few places.. Im not sure if we should remove the property or add back the method.

Also note, some integration tests are using setPerPage().

[GrahamCampbell]

👎 here. The new design has this immutable doesn't it?

[Nyholm]

Okey, Then I'll remove the AbstractApi::$perPage.

Thank you for the feedback

[Nyholm]

oops, Im wrong again.

The ResultPager is using AbstractApi::$perPage. I've updated the integration tests and added a small comment.

[acrobat]

Yes, the resultpager is now the "main" point of entry for paginating results so that's the why the perPage property is not accessable anymore for the api classes. But the resultpager still use this property to do it's job.

See #907 for more context on this.

Thanks for the extra comment and fixed tests!

[acrobat]

Thank you @Nyholm