Thiago Bellini Ribeiro

Hey @stoicsleuth , First of all: > Since overriding methods for pagination is not future-proof We are not planning on breaking API for those in the future. The only reason...

Hi @stoicsleuth , Customizing the `StrawberryDjangoField` should be safe! I don't see any reason to change its current internal API in the near future. For curiosity, why is it breaking...

Ohhh I see. Yeah, I think that is the way to go right now. We do have a similar workaround for connections in https://github.com/strawberry-graphql/strawberry-graphql-django/blob/main/strawberry_django/fields/base.py#L74 Wondering if it would make sense...

Hi @SafaAlfulaij , Indeed the current `get_queryset` is not async safe. Maybe we could wrap everything from that line to the end inside `django_resolver`? If so, it would make sense...

> @bellini666 Yeah, that should be sufficient. @SafaAlfulaij do you want to try to open a PR for that? Otherwise I'll try to take a look at the end of...

> Hello, I would like to use this issue to discuss and hopefully agree on filtering and ordering changes and fixes that I am currently working on. > > ###...

> Django does not like None for some lookups TBH, the current lookups implementation is non optimal for most cases. E.g. it allows one to use `range` for strings/bools What...

> First thing I would like to mention is current implementation of auto for bool field when lookups are enabled for Filter class. Currently type generated is bool not FilterLookup[bool]...

@iamcrookedman I actually like you idea, specially because of the fact that `ordering` cannot be applied sequentially (i.e. the next call to `order_by` will replace the previous one), so your...

Fixed by https://github.com/strawberry-graphql/strawberry-django/pull/478