-
Notifications
You must be signed in to change notification settings - Fork 150
pagination to support entities in b2b #389
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
pagination to support entities in b2b #389
Conversation
|
@nrkapoor @paliarush opened PR for pagination in collection that can impact b2b performance. |
|
@paliarush please advise for backward compatibility, will convert it into PR once we resolve it. |
fd7d860 to
eb5b7b3
Compare
|
@dani97 Hey! Just an FYI, @paliarush is out of the office right now, and I'm a bit backed up on reviews of other things. We'll try to get to this one, but expect some delays. This is a very important change though, and I'm glad you're starting the discussion! |
|
@dani97 please move the PR from |
eb5b7b3 to
427ef5b
Compare
| @@ -0,0 +1,25 @@ | |||
| type Cart { | |||
| items( | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we need field type change, a new field with version suffix should be introduced, items_v2 in this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same is related to other entities in this list.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we deprecate the field?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, let's deprecate the old fields.
| @@ -0,0 +1,25 @@ | |||
| type Cart { | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When possible, please locate the original proposal with the schema and modify it there (like it is done for customer-orders). Thanks
427ef5b to
092cf63
Compare
|
@paliarush made the changes 👍 |
design-documents/graph-ql/coverage/customer-address-pagination-change.graphqls
Outdated
Show resolved
Hide resolved
design-documents/graph-ql/coverage/customer-address-pagination-change.graphqls
Outdated
Show resolved
Hide resolved
|
Please resolve the merge conflicts. |
1054404 to
b28e922
Compare
design-documents/graph-ql/coverage/customer-address-pagination-change.graphqls
Outdated
Show resolved
Hide resolved
|
@melnikovi resolved and added pagination to wishlist |
Problem
Current Graphql endpoints like cartItems, address, order items etc are not paginated. In B2B scenarios, these could impact performance because of large number of items will be returned in collection.
Solution
Adding pagination for entities.
Cart Items,
Order Items,
Customer Addresses
Requested Reviewers
@nrkapoor
@paliarush
@DrewML