Pavel Nikolov
Pavel Nikolov
You can always treat errors as data and add them to your schema. Otherwise, how do you imagine subscriptions? Sent from my phone > On 9 May 2019, at 11:22,...
I'm looking into the PR. I'm sorry I didn't understand the problem earlier.
There is a pending conflict and question... 👀
As a beginning, send the subscription error propagation first in a separate PR.
Thanks! I think this PR has to, actually, be split into 2 PRs. One for refactoring and another one to add validation for these types. This would make it much...
@romshark thank you for your contribution. I am happy with your PR and I'd be happy to merge it. However, there is one problem with it - it introduces a...
@romshark I'd be happy with that idea. And then have `Validate` call `ValidateWithArgs` passing `nil` for args.
@ssko1 feel free to take it and resolve the conflicts
I am not convinced that this should be part of the library. You can have your errors treated as data and have them in your schema resolver as fields. For...
@jdutil yes, partially. I think now there is a pull request that has the issue fixed. Also you can take a look at quick and dirty solution I have in...