Skip to content

Editorial: consistent field ordering in Circular References examples#1214

Merged
benjie merged 1 commit intographql:mainfrom
jbellenger:jbellenger-editorial-circular-ref-field-order
Mar 9, 2026
Merged

Editorial: consistent field ordering in Circular References examples#1214
benjie merged 1 commit intographql:mainfrom
jbellenger:jbellenger-editorial-circular-ref-field-order

Conversation

@jbellenger
Copy link
Contributor

@jbellenger jbellenger commented Mar 6, 2026

In the section on Input Object Circular References, there are a number of examples that use the format

input Example {
  self: Example
  value: String
}

Specifically, the input objects define a value: String field that is the second field in the type definition.

One of the definitions reverses the order of the fields, putting the value: String definition first.

This is a pedantic edit to change the ordering so that it has the same field ordering as the other examples in this section.

Suggested by @benjie in #1211 (comment).

Reorder fields in the counter-example for self-referencing input types
so that `self` appears before `value`, matching the field order used in
all other examples in the Circular References section.
@netlify
Copy link

netlify bot commented Mar 6, 2026

Deploy Preview for graphql-spec-draft ready!

Name Link
🔨 Latest commit f13c2e8
🔍 Latest deploy log https://app.netlify.com/projects/graphql-spec-draft/deploys/69ab624b746e88000856b084
😎 Deploy Preview https://deploy-preview-1214--graphql-spec-draft.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@jbellenger jbellenger marked this pull request as ready for review March 6, 2026 23:33
Copy link
Contributor

@martinbonnin martinbonnin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay for consistency 👍

@benjie benjie added the ✏️ Editorial PR is non-normative or does not influence implementation label Mar 9, 2026
@benjie benjie merged commit 3c6695c into graphql:main Mar 9, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

✏️ Editorial PR is non-normative or does not influence implementation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants