graphql / graphql-js / 506

99%

master: 98%

push

travis-ci

Resolvers can return `Error` to signify failure

This adds another way resolver functions can signify a failure: returning an Error object.

The primary reason this is useful is returning a list of values where index contains an error but another does not. A test casehas been added to illustrate this behavior. Previously sync resolvers could only throw an error, killing the whole list, or return nulls and fail to present error messaging.

I then used this as a simplifying factor to the executor core where it removed a third instance of locating and logging an error.

10 of 10 new or added lines in 2 files covered. (100.0%)

4946 of 4978 relevant lines covered (99.36%)

4146.28 hits per line