-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Relay fetch for recursive data without id
s returns null
#742
Comments
Thanks for your question! We want to make sure to keep signal strong in the GitHub issue tracker – to make sure that it remains the best place to track issues that affect the development of Relay. Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #relayjs? We'll be happy to answer there. Post a link to your Stack Overflow question here, to so that we don't lose track of it. |
I created a stackoverflow for same here. Any insights to issue are greatly welcome or temporary work around for issue if possible. |
Thanks! Let's move discussion to the SO question. |
@josephsavona This is actually a bug, so can you please reopen the issue. |
id
s returns null
id
s returns nullid
s returns null
@shahankit just saw your SO comment - yeah this looks like a bug. I suspect this has to do with the fact that the schema doesn't use the |
You were right all along. This was a bug. Fixed in #1243 |
@steveluscher thanks. |
I have a recursive data structure to be fetched and displayed. I have a graph ql type as follow:
Now I wanted to incrementally fetch data and hence used to react classes HumanList and HumanItem, where I've used relay to fetch children only when a item is clicked. In my actual code relay gives children a null on very click i.e. on rendering very first set of children. I tried test code on relay playground and found similar issue. Here is the link to gist. Playground.js contains the code part and Playground.gql.js contains schema part.
I've already checked #246 and #536 but none of them helped.
The text was updated successfully, but these errors were encountered: