Skip to content
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

(graphql) Opt out from Relay Style spec #7412

Closed
1 of 3 tasks
axelhildingson opened this issue Jun 2, 2021 · 3 comments
Closed
1 of 3 tasks

(graphql) Opt out from Relay Style spec #7412

axelhildingson opened this issue Jun 2, 2021 · 3 comments

Comments

@axelhildingson
Copy link

Current Limitation

We use apollo client and it is possible select your own field that will be use as cache key so we decided to use objectId instead of id. We can't see any use of the connection logic from relay, it just adds a bunch of logic in the queries that we don't use.

So is possible to opt out of the relay node interface? I can see that you discussed in this PR #5863 but I cant find any information about it in the docs and I can't find anything in the code that indicate that this is possible.

Feature / Enhancement Description

Make it possible to opt out of Relay, Node, Connection and Cursor and Id.

@davimacedo
Copy link
Member

No. It is not possible to opt out the Relay style spec. We turned out deciding to go with a single style (Relay style) which is actually a fit for both Relay and non Relay apps.

@axelhildingson
Copy link
Author

Ok, thank you for fast answer 👍, we will probably carry on our migration as long as you can use objectId as id 😃 ( we have built a lot of logic around objectId so it will be hard for us to change it to id )

@davimacedo
Copy link
Member

actually most of the queries and mutations accept both id and object id.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants