Respect query object field order

[ck3d]

Description of the feature

According to GraphQL specification the object field order in a query should be respected:

GraphQL Objects represent a list of named fields, each of which yield a value of a specific type. Object values should be serialized as ordered maps, where the queried field names (or aliases) are the keys and the result of evaluating the field is the value, ordered by the order in which they appear in the query.
https://spec.graphql.org/June2018/#sec-Objects

In the current implementation the fields are alphabetically sorted.

[sunli829]

Yes, but I think this does not seem to be important? If you really need this, please tell me why. 🙂

[ck3d]

I do not rely on this behavior, but I was astonished while comparing Juniper with your great implementation.

[gyzerok]

@sunli829 while I am also not sure why this might be important, I think it does make sense to follow specification strictly. That's the goal of having spec, isn't it? 😄 There could be tools which might rely on this behavior and it might be tricky to debug why something isn't working in this case.

Imagine someone who is using async-graphql with library X on the frontend. This someone might not know GraphQL spec to the word. Now this someone gets unexpected behavior from library X. They could spend hours trying to figure out what's wrong.

Also, to be honest it breaks my head a bit, when I am working in the playground. Because it's a bit hard to match what I see in the query and what I see in the response.

[sunli829]

@sunli829 while I am also not sure why this might be important, I think it does make sense to follow specification strictly. That's the goal of having spec, isn't it? 😄 There could be tools which might rely on this behavior and it might be tricky to debug why something isn't working in this case.

Imagine someone who is using async-graphql with library X on the frontend. This someone might not know GraphQL spec to the word. Now this someone gets unexpected behavior from library X. They could spend hours trying to figure out what's wrong.

Also, to be honest it breaks my head a bit, when I am working in the playground. Because it's a bit hard to match what I see in the query and what I see in the response.

You are right, I will support this now. 🙂

[sunli829]

Released in v2.10.6.🙂

[ck3d]

Thanks a lot!