Unexpected order of properties in response

[EmrysMyrddin]

The problem

GraphQL operation results content should be stable, in particular the field order should be respected based on the query. This is a requirement of the GraphQL spec

Discussed in #3218

^{Originally posted by marceloverdijk March 31, 2024}
I noticed having a query like:

query MyQuery {
  countries(first:100) {
    totalCount
    nodes {
      code
      name
      continent {
        name
      }
    }
  }
}

the response is:

{
  "data": {
    "countries": {
      "totalCount": 249,
      "nodes": [
        {
          "name": "Afghanistan",
          "code": "AF",
          "continent": {
            "name": "Asia"
          }
        },
        {
          "name": "Åland Islands",
          "code": "AX",
          "continent": {
            "name": "Europe"
          }
        },
  ..

In the response I would expect the order of the fields in the same order as requested.

But in the response the name field is before the code field.

This is quite annoying when testing an server, or even thinking about exposing a GraphQL service to (semi) business people that e.g. before used SQL to query data.

Is this something that can be configured?

[enisdenjo]

Can we get a repro? What does the schema with resolvers look like?

[kruckenberg]

Here's a reproduction. The README also identifies the cause of the bug.

If no one minds, I can work on a test and fix.

[Urigo]

Thank you @kruckenberg for getting us to stage 1 thanks to your reproduction according to our new Contribution Guide and issue flow!

Now in order to advance to stage 2 we'll need a failing test, would be great if someone could help progress the issues through the stages.

Thank you and sorry that this comment is not a complete solution (yet).

[enisdenjo]

Oh and, no one minds! We'd greatly appreciate if you give the fix a go. We're here to assist if necessary.