My team is using the Apollo client for Ember.
We a...
# orm-helps
shawneegao
12/20/2018, 8:04 PMMy team is using the Apollo client for Ember.
We are trying to figure out a better pattern for making paginated queries. (Hope this is a good place to ask!)
Currently we have a service that queries a paginated list of Type Cases. Cases are the leaf nodes of a heavily nested query (part of a complicated business object).
Currently my team is using 3 methods to manage 1 paginated endpoint:
1. queryCases for making the initial watchQuery call (returns a query reference)
2. loadMoreCases to call fetchMore and updateQuery (returns a query reference)
3. getNodes helper function to return the actual nodes. I believe the model using the service shouldn’t have to know the structure of the graphql query.
This feels like an inefficient implementation/not really great developer experience. Are there better pattern suggestions?
a
Alan
01/02/2019, 11:10 PMHey! in your generated file (with prissa) you have 2 queries:
Alan
01/02/2019, 11:10 PMusers(where: UserWhereInput, orderBy: UserOrderByInput, skip: Int, after: String, before: String, first: Int, last: Int): [User]!Alan
01/02/2019, 11:10 PMand
Alan
01/02/2019, 11:10 PMusersConnection(where: UserWhereInput, orderBy: UserOrderByInput, skip: Int, after: String, before: String, first: Int, last: Int): UserConnection!Alan
01/02/2019, 11:14 PMwith the second one, you have everything to create your own pagination in
pageInfoAlan
01/02/2019, 11:14 PMAlan
01/02/2019, 11:15 PMyou have an example here: https://github.com/alan345/naperg
Alan
01/02/2019, 11:15 PM2 Views