Tommy Smith

Hi @pepilipep, thanks for raising this bug with my implementation :smile: To be clear, however, does your `request` attribute within your `CustomContext` itself inherit from `Request`? By which I mean,...

This is an interesting side-effect of the current implementation! In my understanding, the problem arises due to https://github.com/strawberry-graphql/strawberry/blob/main/strawberry/fastapi/router.py#L216 where, as you say, any `yield` functionality in the `self.context_getter` is resolved...

I guess the misunderstanding that you're highlighting here is about clarifying the scope of the behaviour of `Depends`. I would say that, since it is part of the FastAPI functionality,...

I'm afraid you will need to provide a concrete example of some code that is behaving in a way that you do not expect as our discussion so far is...

@fabiob, is there any chance this could be merged? It would be a great change that makes spinning up standalone docker compose environment much easier. Cheers!

@kristjanvalur, revisiting this issue in the context of the linked PR is helping my understanding with regards to the problem. Indeed, it seems that this issue may be closely related...

Your comment on dependencies being essentially pointless, I've seen echoed elsewhere. So I'd like to get into the weeds on this problem and hopefully find a nice solution. Potentially leveraging...

@patrick91, there seems to be a similar issue as I just linked. I will look into how the GraphiQL interface passes request-level data to the FastAPI server and the `context_getter`...

Here's an MRE that I'm using for anyone else to try: ```python import asyncio import strawberry from strawberry.fastapi import BaseContext, GraphQLRouter from strawberry.types import Info from fastapi import Depends, FastAPI,...

So, @s3rius, it appears that this is in fact an issue with FastAPI itself when using sub-dependencies within a parent class dependency over a websocket connection: https://github.com/tiangolo/fastapi/issues/2031. The OP in...