exAspArk/graphql-errors issues and pull requests

#21 - Add a deprecation error message

Pull Request - State: closed - Opened by exAspArk over 4 years ago - 1 comment

#20 - Couldn't catch error with [email protected]'s new GraphQL::Execution::Interpreter

Issue - State: closed - Opened by layerssss almost 5 years ago - 2 comments

#19 - Feature: handle rescue_from Module arguments properly

Pull Request - State: closed - Opened by sclinede about 5 years ago - 2 comments

#18 - Makes the gem compatible with GraphQL::Execution::Interpreter

Pull Request - State: closed - Opened by knshiro over 5 years ago

#17 - Compatibility with class based Graphql-ruby?

Issue - State: closed - Opened by ghost over 5 years ago - 12 comments

#16 - CI: use 2.3.8

Pull Request - State: closed - Opened by olleolleolle over 5 years ago - 1 comment

#15 - Travis: less narrow Bundler version

Pull Request - State: closed - Opened by olleolleolle almost 6 years ago - 1 comment

#14 - Rescue from lazy resolution

Pull Request - State: closed - Opened by DamirSvrtan almost 6 years ago - 3 comments

#13 - Test rescuing errors from lazy objects [WIP]

Pull Request - State: closed - Opened by exAspArk almost 6 years ago - 2 comments

#12 - Usage with the batch loader

Issue - State: closed - Opened by DamirSvrtan about 6 years ago - 5 comments

#11 - Add tests for GraphQL-Ruby 1.8

Pull Request - State: closed - Opened by exAspArk over 6 years ago - 1 comment

#10 - Validation errors from model don't show

Issue - State: closed - Opened by RolandStuder over 6 years ago - 2 comments

#9 - Does graphql-errors support graphql-ruby 1.8.0pre / class-based API?

Issue - State: closed - Opened by benkimball over 6 years ago - 9 comments

#8 - add object, argument and context to rescue_from

Pull Request - State: closed - Opened by rodrigosol over 6 years ago - 2 comments

#7 - Access ctx inside error handles

Issue - State: closed - Opened by rodrigosol over 6 years ago - 7 comments

#6 - "\n" in errors message?

Issue - State: closed - Opened by ghost almost 7 years ago - 1 comment

#5 - Can you explain it better in docs where to put the config file?

Issue - State: closed - Opened by ghost almost 7 years ago - 1 comment

#4 - There is something like "NotAuthorizedError"?

Issue - State: closed - Opened by ghost almost 7 years ago - 2 comments

#3 - Remove confusing Notify.

Pull Request - State: closed - Opened by dblock about 7 years ago - 1 comment

#2 - Errors raised via GraphQL::ExecutionError aren't caught by github/graphql-client

Issue - State: closed - Opened by dblock about 7 years ago - 4 comments

#1 - Consider moving to the graphql-ruby org?

Issue - State: closed - Opened by dblock about 7 years ago - 2 comments

Ecosyste.ms: Issues

GitHub / exAspArk/graphql-errors issues and pull requests