graphql
graphql copied to clipboard
Adopt idiomatic error handling for executor.
Stop using panic
/recover
to throw errors. Instead, stick to Go's
style for handling error. Function reports errors by returning an Go's
error
value (instead of passing with panic
). Errors are explicitly
checked or bypassed at where they might occur (instead of checking the
return value from recover
).
Discussion: #28 Related: #44 Invalidate: #243, #253 Close: #402
What's preventing this from being merged?
@egonelbre Could you take a look at this?
Can this get some attention?
@Fontinalis @egonelbre What's left for this to be merged? It's been 7 months, and this is bugging us.
@Fontinalis I made the readability changes I commented in https://github.com/egonelbre/graphql/commit/3e383bec6e59522df4bed6219cf4f2ae11c0fe73, but I have no clue how to get these changes into this PR.
We could always merge as is and I can a do separate PR against.
How long time we must wait to this feature?