为什么在graphene-django中中继？

Question

I would like to know why Relay spec is in graphene-django? I understand that using relay in graphene-django we get pagination and filters by default.

My requirement is to call graphql apis from React (for Web) and use Apollo client for Android and iOS.

1. Will there be a problem for clients to consume graphql apis written using graphene-django with Relay compliant especially pagination (and cursors) feature?

2. How to support subscriptions using graphene-django?

Any help would be highly appreciated.

Answer 1

1. There isn't any problem with consuming Relay-compliant graphene-django API. My team at work is currently using react-query library , and it works fabulously!

2. As mentioned in this graphene-django Github issue , GraphQL subscription is currently not supported out of the box.

Answer 2

Relay is the client-side middleware between React and any GraphQL server. Relay Specs provided by graphene-django just make it easier to use relay with graphene-django. They are not strictly necessary

1. There should not be a problem for clients to consume graphql apis written using graphene-django

2. Subscriptions are handled by a separate package - graphene-django-subscriptions