Ok true :thumbsup: And I was wrong, ContextWebFilt...
# graphql-kotlin
r
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:
Copy code
val reactorContext =
    coroutineContext[ReactorContext]?.context
in a resolver function won't return the context
d
problem is due to the reliance on graphql-java….
basically it needs completable future which means that underlying call chain is broken
and you won’t get anything in reactor context
r
True, I noticed when inspeciting the parent contexts
d
i.e. reactor (router) -> coroutine (handler) -> completable future (graphql-java) -> coroutine (resolvers)
would love to have kotlin native execution but didn’t get a chance to work on it yet