GraphQL: Change Order Enum Strategy

[Moumouls]

Due to ardatan/graphql-tools#1206, enums with custom value are not correctly merged and lead to bugs and validation error.

We need to transform GraphQL Order to Parse Order later before sending request to Parse Server.

This bug only occur on merged schemas.

[davimacedo]

Great job!

[codecov]

Codecov Report

Merging #6515 into master will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #6515      +/-   ##
==========================================
+ Coverage   94.01%   94.03%   +0.02%     
==========================================
  Files         169      169              
  Lines       11825    11866      +41     
==========================================
+ Hits        11117    11158      +41     
  Misses        708      708              

Impacted Files	Coverage Δ
src/GraphQL/loaders/parseClassQueries.js	97.91% <ø> (-0.05%)	⬇️
src/GraphQL/helpers/objectsQueries.js	91.33% <100.00%> (+0.58%)	⬆️
src/GraphQL/loaders/parseClassTypes.js	94.15% <100.00%> (-0.08%)	⬇️
src/Adapters/Auth/apple.js	100.00% <0.00%> (ø)
src/Adapters/Auth/instagram.js	100.00% <0.00%> (ø)
src/middlewares.js	97.36% <0.00%> (+0.16%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2c10d9e...df1b65f. Read the comment docs.

[yaacovCR]

A more long term approach would be to use https://www.npmjs.com/package/graphql-tools-fork, following gatsby and graphql-toolkit. Happy to help

[davimacedo]

That would be great @yaacovCR . Feel free to open a PR.

[yaacovCR]

Sounds good, does this change come with any failing tests to check?

[davimacedo]

No failing tests were added. That's my bad. I should had requested @Moumouls to do so. But I was able to reproduce this issue myself. You just need to extend the graphql auto schema and then perform any sort in any query. I can try to write something if you need it.

[yaacovCR]

I kind of need it. :) I want to be sure when I switch to fork and revert this patch that it still all works.

[davimacedo]

Just sent the PR: #6537

You can continue the development over that branch

[yaacovCR]

This is now fixed in upstream graphql-tools as well in v5 which merges fork.

[yaacovCR]

See #6611