Patrick Arminio

thanks for this! do you have an example of the code you used for the benchmarking? I'll add it here: https://github.com/strawberry-graphql/benchmarks

/pre-release

I mostly like this, the only two things I don't like are, from this example: ```python @strawberry.type class Query: @PaginatedField() def books() -> List[str]: return [ "Pride and Prejudice", "Sense...

don't really like this option ```python @strawberry.type class Query: @strawberry.field(implementation=PaginatedField) def books() -> List[str]: return [ "Pride and Prejudice", "Sense and Sensibility", "Persuasion", "Mansfield Park", ] ``` maybe we can...

> > maybe we can do what asgi ref does with sync_to_async? :D > > Sure thats fine. I think the built in custom fields we should expose as lower...

interesting! I wonder if this is a bug in graphql-core or in strawberry. I'll mark this as a bug anyway, thanks for reporting it!

@jaydenwindle thanks for answering 😊 at PyCon DE someone asked for Relay support, maybe we could write some helpers for that, I kinda this something here: https://github.com/strawberry-graphql/strawberry-swapi/blob/master/utils.py I think Graphene...

@denizdogan what did you try already? I'd like to know mainly because I'd like to make the library as user friendly as possible :) I'll try to come up with...

oh, when we use `@strawberry.field` we add an attribute on the function, so that we can find it later (to created the field), but maybe this approach is not the...

Quick update on this, we recently released support for generic types with the goal of making it easier to create pagination types. They'd work like this: ``` import strawberry @strawberry.type...