Closed rafaelhbarros closed 6 months ago
self
inside resolvers can sometimes not be what you are expecting: https://strawberry.rocks/docs/types/resolvers#defining-resolvers-as-methods
That being said, I'm not actually seeing anything wrong with your example. It seems that something failed to await the result of create_recording_streaming_info
and passed the coroutine itself as the root to the resolver below it.
Could you try to provide a MRE of the issue?
I'll produce a reproducible example today. The documentation is peculiar too.
Okay, I wrote an example but it works in this version. I have no idea why. I'll keep seeing if there is something I am missing on one of these.
@bellini666 I found the issue, it's an extension we have for auth. I'll close this ticket.
@rafaelhbarros awesome! :)
Feel free to open more issues in case you find anything else.
Also:
The documentation is peculiar too.
Let us know how we can improve the docs. Also feel free to open any PRs for docs improvements if you want/can. That's something I really need to do in this lib...
A mutation was written in django with a payload that returns multiple values, defined as:
And I get this error:
If I write:
(await self)._is_error
and(await self)._is_expired
for instance, it says coroutine is already being awaited.Why is
self
a coroutine?Upvote & Fund