Ok true :thumbsup: And I was wrong, ContextWebFilt...

# graphql-kotlin

[Robert]

Ok true 👍 And I was wrong, ContextWebFilter is for incoming and ExchangeFilterFunction for the outgoing requests via WebClient. However, the Reactor/Security Context (also GRAPHQL_CONTEXT_KEY) is not present there.
The requests outside of graphq-kotlin handling have a populated Context.


The Problem is also there outside of the FilterFunction.

Using:

val reactorContext =
    coroutineContext[ReactorContext]?.context

in a resolver function won't return the context

[Dariusz Kuc]

problem is due to the reliance on graphql-java….

[Dariusz Kuc]

basically it needs completable future which means that underlying call chain is broken

[Dariusz Kuc]

and you won’t get anything in reactor context

[Robert]

True, I noticed when inspeciting the parent contexts

[Dariusz Kuc]

i.e.
reactor (router) -> coroutine (handler) -> completable future (graphql-java) -> coroutine (resolvers)

[Dariusz Kuc]

would love to have kotlin native execution but didn’t get a chance to work on it yet