Pagination example is unclear in GetOrdersRequest

[shrink]

For GetOrdersRequest::class the example mentions pagination:

/**
 * (OR11) Retrieve orders
 *
 * Sort by creation date, order identifier, shop name and then by index of the order line
 * This API uses pagination by default and will return 10 orders
 *
 * Example:
 *
 * <code>
 * use Mirakl\MMP\Shop\Client\ShopApiClient;
 * use Mirakl\MMP\Shop\Request\Order\Get\GetOrdersRequest;
 *
 * $api = new ShopApiClient('API_URL', 'API_KEY', 'SHOP_ID');
 * $request = new GetOrdersRequest();
 * // Optional parameters
 * $request->setOrderIds(['ORDER_ID_1', 'ORDER_ID_2'])
 *     ->setOffset(10)
 *     ->setMax(25)
 *     ->setPaginate(false)
 *     ->setStartDate('2015-06-09')
 *     ->setEndDate('2015-06-30');
 * $result = $api->getOrders($request);
 * // $result => @see \Mirakl\MMP\Shop\Domain\Collection\Order\ShopOrderCollection
 * </code>
 */

However, if we look in AbstractRequest::class we can see that setPaginate(false) means that max and offset are ignored:

        /** @see PageableTrait */
        if (is_bool($this->getPaginate())) {
            $params['paginate'] = $this->getPaginate() ? 'true' : 'false';
            if ($this->getPaginate()) {
                $params['max'] = $this->getMax();
                $params['offset'] = $this->getOffset();
            }
        }

I think the example is therefore misleading because setPaginate(false) is preventing the use of the values provided in setMax() and setOffset(). I am creating this as an issue rather than with a proposed change in a Pull Request as I am not confident that my understanding is correct, because the API does accept a paginate parameter which is described as...

paginate optional boolean Control the pagination usage Default to true

So it seems possible to completely disable pagination for this endpoint (and therefore get all results, independent of the max?) which would indicate that setPaginate(false) does have some intended influence on how the API responds. Unfortunately, we don't have enough orders in our Mirakl instance to test the behaviour of the API when there's more than 100 results.