These are chat archives for graphql-java/graphql-java

24th
May 2017
Bojan Tomić
@kaqqao
May 24 2017 17:13
Is there a way to throw an exception from within an instrumentation in a way that will stop further execution, but not bubble up all the way to the top? I.e. I want to throw an exception, but still receive the (partial) ExecutionResult
Basically get the same behavior you get when throwing an exception from a DataFetcher
Andreas Marek
@andimarek
May 24 2017 17:27
@kaqqao no there is not
but I will work on something similar very soon, so please feel free to create a issue ... maybe we can do that without much effort
Bojan Tomić
@kaqqao
May 24 2017 17:58
Looked into the code a bit... For my case, it would be enough to just move the beginFieldFetch call into the fetcher's try block.
Bojan Tomić
@kaqqao
May 24 2017 18:19
But that may not be what you want to do. I'll open an issue.
Bojan Tomić
@kaqqao
May 24 2017 21:49
Opened #460
Bojan Tomić
@kaqqao
May 24 2017 21:57
If you want to discuss the approach and delegate it to me, I'd gladly pitch in
Brad Baker
@bbakerman
May 24 2017 23:07
I cant recall the spec saying that query execution is optional and can be shortcut. While an engine is free to do what it wants beyond the spec…its interesting….