-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Order History - Customers can only view up to 20 orders in their order history #6032
Comments
➤ Vladyslav Vakhnovskyi commented: Igor Wojciechowski Mike Kwiatkowski Following the CT spec (https://docs.commercetools.com/api/general-concepts#limit ( https://docs.commercetools.com/api/general-concepts#limit|smart-link ) ): {quote}Limit The maximum number of results to return from a query can be set using the limit query parameter. Allowed is a value between 1 and 500. The default limit on most query endpoints is 20.{quote} I assume that in order to be able to explore the full order history, some sort of pagination needs to be implemented for the order history items. This can be done by providing additional query parameters (limit, offset, ...) and additional functionality to handle the movement of the pagination. Could you please confirm if this approach is suitable and should be implemented. Thank you. |
➤ Patrick Andrew commented: Vladyslav Vakhnovskyi Yeah, would be nice to have pagination here. Please implement in in commercetools theme. You can even copy and paste entire account management to the Commercetools (from core) if you will be forced to do it (we will have custom templates anyway) |
➤ Alef Barbeli commented: #6108 ( https://github.com/vuestorefront/vue-storefront/pull/6108|smart-link ) |
➤ Łukasz Jędrasik commented: #6290 ( https://github.com/vuestorefront/vue-storefront/pull/6290|smart-link ) |
Expected result
Customer should be able to view more than just 20 of their orders
Actual result
Customer can view only up to 20 orders in order history
Steps to reproduce
The text was updated successfully, but these errors were encountered: