Root resolver returning undefined or null doesn't stop execution about graphql-tools

[helfer]

Actually, on second thought, I think this is perfectly reasonable. If execution should stop in the root resolve function, an error should be thrown.

[BransonGitomeh]

how do i handle the resolvers that need values sent from parents above them?. returning failure on the parent leads to a cascading faulire in all the children since they don't get the values they expect. whats the best way to just stop execution on the parent and return an error, from that first resolve?

[helfer]

@BransonGitomeh for all resolvers apart from the simulated root resolve function (which you shouldn't use unless you have a good reason for it), returning null or undefined will do the trick. For the root resolve function you need to throw an error to stop execution.