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 https://github.com/rmosolgo/graphql-ruby/pull/2140 but looking at the stacktrace I think it may be due to the addition
use GraphQL::Execution::Interpreter
: