Apollo-ios: Handling of Relay connections

Created on 18 Sep 2017 · 8Comments · Source: apollographql/apollo-ios

Hey.

It will be really good if the client has a way to handle connections. As far I understand it, if I want to render an infinite scroll table view that is fed via a connection, I have to handle this completely in my code. I'm uncertain how that interacts with the cache (I assume it doesn't). It feels like a generic enough case to deserve some support in the client.

I've asked @martijnwalraven about this in the GraphQL Slack's #swift channel and he suggested I open an issue. I'd be happy to attempt a pull request (and figure out the code), but I certainly need some architectural guidelines on how the API should look and behave. @martijnwalraven also mentioned that this would be a good place to discuss how this change should look.

enhancement

Source

skanev

👍17

Most helpful comment

This is definitely something we should support, especially for larger queries.

designatednerd on 25 Jun 2019

👍6

All 8 comments

Would love to see this added. This is core to scrolling list views.

ocrickard on 11 Oct 2017

For pagination support in general, I'd like to stay as close as possible to Apollo JS, because something like fetchMore doesn't tie us to Relay connections specifically.

There are a few things I think we can do to make dealing with those more convenient however, both in the generated code and in the runtime:

Adding conformance to a Connection protocol to the generated types would give us a way to treat connections generically and add extension methods.
I'd also like to add support for the @connection directive that both Relay and Apollo JS support to generate a stable caching key that ignores pagination parameters.