adds a field sort by source location before executing serially

[bhoriuchi]

Resolves #145 by sorting fields by source location before executing serially

[coveralls]

Coverage increased (+0.03%) to 92.378% when pulling b6b24cf on bhoriuchi:master into d925012 on graphql-go:master.

[djmcgreal-cc]

I'd love this to get some attention from reviewers. Not having mutations executed in the correct order means that we go back to needing multiple operation requests to enforce order of a chain of mutations.

Personally, I'd also like to see this configurable to be usable outside of the top level of a mutation operation. Our schema wraps every operation in an authenticate field so it's actually the second level of fields we would like executed in serial.

Perhaps there should also be a test case for this.

[chris-ramon]

@bhoriuchi thanks a lot for improving the serially execution order! –– it definitely looks good to me 👍 💯

I've tested it and seems working neat! –– Sharing the gist with the working example: https://gist.github.com/chris-ramon/6c98e31259d1c7837fc3f240ee4f988d

[chris-ramon]

I'd love this to get some attention from reviewers. Not having mutations executed in the correct order means that we go back to needing multiple operation requests to enforce order of a chain of mutations.

Personally, I'd also like to see this configurable to be usable outside of the top level of a mutation operation. Our schema wraps every operation in an authenticate field so it's actually the second level of fields we would like executed in serial.

Perhaps there should also be a test case for this.

@djmcgreal-cc thanks a lot for the feedback! 👍 –– perhaps could you file an issue and share an example of the query your mentioning, so we could make this PR configurable via a follow-up PR.

[chris-ramon]

LGTM 👍 –– Neat improvement @bhoriuchi 💯 🚢