New context API doesn't make sense?

[Anthonyzou]

So I have instrumentation that accesses the context but the new API always returns an empty map.

I am using the ktor web server and I have a factory to generate the context but how can I possibly set the context using the new API?

>

[smyrick]

Your question is specific to the new graphql-java 17 context object. You can find out more info about that here: graphql-java/graphql-java#2368

[Anthonyzou]

That kind of helped, but I figured out the issue. It is not possible to remove the .context call from ExecutionInput.

Basically without the .context call the library will think GQLContext is an input type instead of a context to inject.
How will the context get injected in the future if it becomes deprecated?

[smyrick]

We will most likely deprecate our GraphQLContext interface in favor of just getting the DataFetchingEnvironment but we also wanted to see how the spring-graphql integration would look as we would like to adopt that over our current custom implementation. Once we know how we can best have the generator hook into that project, we will be making more changes.

In the meantime, if you wanted to use the new context map instead of the deprecated context object, you can do this

fun test(dfe: DataFetchingEnvironment): Boolean {
  return dfe.graphqlContext.get("name") == null
}

[dariuszkuc]

Support for new GraphQL context is added through #1292