yaacovCR / graphql-tools-fork / 238

89%

master: 90%

push

travis-ci

refactor(testUpload)

Simply example usage within test.

Inclusion of the GraphQLUpload scalar within the resolver map is only necessary when merging an executable "local" subschema, as if the subschema has the original GraphqlUpload scalar defined, it will throw when attempting to serialize after it is merged into the gateway. The custom GraphqlUpload scalar can be used in that case to avoid that either within the local subschema or within the gateway.

In this case, the subschema is remote, and so the subschema custom scalar is imported with the default serialize method that does not throw.

1198 of 1438 branches covered (83.31%)

Branch coverage included in aggregate %.

2738 of 2942 relevant lines covered (93.07%)

1034.17 hits per line