graphql / graphql-js / 2585

98%

master: 98%

push

travis-ci

Improve errors when receiving bad introspection data

I've seen a few examples of passing bad introspection data to buildClientSchema() result in a hard to understand internal error. This instead prints a more understandable error which includes a print out of the bad value in question. Hopefully this aids debugging.

This also adds a comment to the description of this function recommending that the "errors" field of a server response be checked before continuing to avoid partial results.

3767 of 4248 branches covered (88.68%)

26 of 26 new or added lines in 1 file covered. (100.0%)

9162 of 9357 relevant lines covered (97.92%)

1249.79 hits per line