Lukasz Piatkowski

Just friendly pinging @patrick91 here :)

# Yet another workaround I didn't like the decorator approach as it required marking every object explicitly with it. Instead I added this code just after schema creation: ```python def...

@patrick91 friendly ping :)

@erikwrede not sure what you are proposing as this solution is changing the overload case for when the resolver is passed. Introducing the Resolver type is the core of this...

It would be nice if you ensure that using subclasses of `Info` is supported. Our use case is having our own custom class to have better types on the `context`...

This is a major flaw in the libary IMO. My current workaround is to use `strawberry.unset.UnsetType` directly, like so: ``` from strawberry.unset import UnsetType def foo(id: str | None |...

The solution (for me) is to include `strawberry.ext.mypy_plugin` in mypy.ini configuration, like strawberry itself does here: https://github.com/strawberry-graphql/strawberry/blob/906c9451065eeeb3aa80edebf5dec889d90b71ae/mypy.ini#L1-L3