Hi there, I was wondering, do you already have any plans on how to deal with the `GraphQLContext` ch...

# graphql-kotlin

[Henrik Friedrichsen]

Hi there, I was wondering, do you already have any plans on how to deal with the GraphQLContext changes in graphql-java? Will graphql-kotlin simply use graphql-java’s GraphQLContext as passing custom object definitions seems to be deprecated?

[Dariusz Kuc]

👋 we will upgrade to the new mechanism but we are waiting for the GA of the graphql-spring to determine whether to adopt it (which will most likely require additional changes)

[Dariusz Kuc]

we currently don't have any ETA on the gql context update

[Henrik Friedrichsen]

Got it, thanks for clarifying 🙂

[Henrik Friedrichsen]

Hmm, I’m currently trying to migrate our projects to the new GraphQLContext object, but since GraphQLContext is part of graphql-java, there is no way to apply the marker interface in graphql-kotlin. Should the schema generator maybe also ignore graphql-java’s GraphQLKotlin by default as an intermediate?

[Dariusz Kuc]

we haven't looked into the required updates

[Dariusz Kuc]

updating generator is one thing, another would be also updating the default data fetchers to resolve the arguments and yet another thing on how to populate it

[Dariusz Kuc]

we are always open to contributions 😉

[Dariusz Kuc]

You can also use data fetching env to get the context object (which should already be supported)

[Henrik Friedrichsen]

Sure, will definitely submit a PR if I come up with a good approach 😉 Thanks for the data fetching env suggestion.