QS for django field

[patrick91]

Similar to what we do for filters, we could allow people to add a static qs to fields:

@strawberry.type
class Query:
    posts: list[PostType] = strawberry_django.field(Post, queryset=Post.objects.published())
    all_posts: list[PostType] = strawberry_django.field(Post, queryset=Post.objects.all()) # with permission

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[bellini666]

I like this! :)

My only suggestion here would be to receive the queryset as a callable instead of the queryset directly. The queryset has some stateful behaviours, meaning that if we are using the same one all the time it might product some weird issues.

That could either be a queryset: Callable[[], QuerySet] or queryset: Callable[[Info], QuerySet]. Probably the second one is better, which allows some common dynamic usage, like filtering it by the current user, etc

[devkral]

this is currently be done with the resolver and afterward is get_queryset of in my case ContentNode (the graphql pendant to Content) applied. What is the advantage of the new way?

e.g.

    @strawberry_django.connection(strawberry.relay.ListConnection[ContentNode])
    def contents(
        self,
        info: Info,
    ):
        return Content.objects.all()

[patrick91]

Passing a callable would be the same as using a resolver, so what @devkral mentioned 😊

I think we could keep it simple and only allow static querysets, as a convenience feature :)