Jonathan Kim

@nrbnlulu any refactoring should definitely be in it's own PR because it becomes complicated to review both new features and refactoring at the same time. I'm happy to spend some...

@bperkins24 it's not really possible to support resolvers in any kind of strawberry type serialisation because resolvers have to be called in the context of a GraphQL execution since they...

FYI my intention with #920 was that it would eventually replace the `permission_classes` argument with a custom field.

@nrbnlulu I would probably create a new one because it's very out of date. Most of the changes in that PR are just internal refactoring changes (type -> resolved_type so...

@tyoung-patreon this is the expected behaviour because you are using a lock which effectively forces the execution to be synchronous and so `await loader.load(i)` only gets called sequentially after after...

@tyoung-patreon that execution order you outlined looks correct and I'm also seeing the batching of 3 that you are. I'm not sure exactly why it's batching in 3s but it...

@tyoung-patreon I think the best way to support that is to use something like a Queue that I outlined here: https://github.com/strawberry-graphql/strawberry/issues/2186#issuecomment-1253491395 Essentially you want to do all the work that...

@wakemaster39 docs have been updated here: https://github.com/graphql-python/graphene/pull/1190

@samarthkathal it should be possible to define an input type of `List(MyInputType)` to a mutation. Does that not work?

Thanks for the feedback @Pegase92 . I agree that documentation doesn’t do a good job of giving examples on how to solve issues that you might come across. I was...