-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Refactor (www): Use nodes
in gatsbyjs.org code instead of edges.node
#21255
Comments
@tesseralis Awesome, interested in contributing I'd like to grab it. |
@b0nbon1 sure, go ahead! |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |
Summary
Since Gatsby v2.2.0, it's been possible to use
nodes
instead ofedges.node
in GraphQL queries. All instances of:can be replaced with:
The code that iterates over these can also change from
to:
Motivation
Code cleanliness of the gatsby website. Using up-to-date examples in our codebase can help guide people in showing good patterns, even if our docs can't update those examples due to back-compat issues.
The text was updated successfully, but these errors were encountered: