Nil related error on @types[node] after upping from 2.0.27 to 2.1.0

[svoop]

I've checked the CHANGELOG which contains a few breaking changes, but none of it sounds related to me. However, I have to admit that I'm not doing much using graphql as of now... which is why I don't quite see whether this is my bad or an issue of the graphql-2.1.0 gem.

The exception is:

undefined method `[]' for nil:NilClass
.../ruby/3.2.0/gems/graphql-client-0.18.0/lib/graphql/client/query_typename.rb:28:in `add_typename'

    23|             @types = types
    24|             super(document)
    25|           end
    26|
    27|           def add_typename(node, parent)
=>  28|             type = @types[node]
    29|             type = type && type.unwrap
    30|
    31|             if (node.selections.any? && (type.nil? || type.kind.interface? || type.kind.union?)) ||

The query is not very fancy:

module AIPP
  module NewayAPI
    HttpAdapter = GraphQL::Client::HTTP.new(ENV['NEWAY_API_URL']) do
      def headers(context)
        { "Authorization": "Bearer #{ENV['NEWAY_API_AUTHORIZATION']}" }
      end
    end
    Schema = GraphQL::Client.load_schema(HttpAdapter)
    Client = GraphQL::Client.new(schema: Schema, execute: HttpAdapter)

    class Notam
      Query = Client.parse <<~END
        query ($region: String!, $series: [String!], $start: Int!, $end: Int!) {
          queryNOTAMs(
            filter: {region: $region, series: $series, start: $start, end: $end}
          ) {
            notamRaw
          }
        }
      END
    end
  end

  (...)
end

variables = {
  region: 'LS',
  series: %w(W B),
  start: aixm.effective_at.beginning_of_day.to_i,
  end: aixm.expiration_at.to_i
}
verbose_info("Querying API with #{variables}")
AIPP::Downloader::GraphQL.new(
  client: AIPP::NewayAPI::Client,
  query: AIPP::NewayAPI::Notam::Query,
  variables: variables
)

Any ideas what I'm missing here?

Thanks a bunch!

[rmosolgo]

Hi! The legacy API we removed in 2.1 is still in use inside graphql-client, see https://github.com/github/graphql-client/issues/310

For now, I recommend staying on 2.0.x until that issue is addressed.

[svoop]

@rmosolgo Thanks for the hint, pinned it to 2.0.x for now as you suggested.