You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was on 1.2.2, graphql 1.8.10 and just upgraded to 2.0 and graphql 1.11.5 and see that:
rescue_fromGraphQL::Guard::NotAuthorizedErrordo |e|
# some handlingend
Is not hit when said error is raised.
At first I thought it may be due to rmosolgo/graphql-ruby#2140 but looking at the stacktrace I think it may be due to the addition use GraphQL::Execution::Interpreter:
The text was updated successfully, but these errors were encountered:
sshaw
changed the title
Upgraded to 2.0 And Cannot rescue_from GraphQL::Guard::NotAuthorizedError
Upgraded to 2.0 And Cannot rescue_from GraphQL::Guard::NotAuthorizedErrorOct 14, 2020
Had a chance look into this a bit more and see that one can now catch the error via a proc to instance of GraphQL::Guard as mentioned here. Seems a counterintuitive but maybe there's a good reason?
At the least this should be added to docs on upgrading.
Was on 1.2.2, graphql 1.8.10 and just upgraded to 2.0 and graphql 1.11.5 and see that:
Is not hit when said error is raised.
At first I thought it may be due to rmosolgo/graphql-ruby#2140 but looking at the stacktrace I think it may be due to the addition
use GraphQL::Execution::Interpreter
:The text was updated successfully, but these errors were encountered: