Query & Mutation in namespaces

[axieum]

Describe the Bug

As per the documentation, https://strawberry.rocks/docs/general/mutations#nested-mutations

@strawberry.type
class Query:
    @strawberry.field(description="Query fruits")
    def fruits(self) -> FruitQuery:
        return FruitQuery()

@strawberry.type
class Mutation:
    @strawberry.field(description="Mutate fruits")
    def fruits(self) -> FruitMutation:
        return FruitMutation()

Raises FruitMutation.__init__() missing 3 required keyword-only arguments: 'create', 'update', and 'delete'

I also tried the following variant to no avail.

@strawberry.type
class Query:
    fruits: FruitQuery= strawberry.field(resolver=FruitQuery, description="Query fruits")

@strawberry.type
class Mutation:
    fruits: FruitMutation = strawberry.field(resolver=FruitMutation, description="Mutate fruits")

Raises Query fields cannot be resolved

---

The only thing that appears to be correct, is the GraphiQL schema, in all scenarios it is correct - but that would be due to the type hinting I assume.

---

This works:

from . import models
from .types import Fruit

@strawberry.type
class FruitQuery:
    @strawberry_django.connection(ListConnectionWithTotalCount[Fruit])
    def all(self) -> list[models.Fruit]:
        return models.Fruit.objects.all()

This does not work:

@strawberry.type
class FruitQuery:
    all: ListConnectionWithTotalCount[Fruit] = strawberry_django.connection()

Query fields cannot be resolved. Argument type must be a GraphQL input type.

System Information

• Operating system:
• Strawberry version (if applicable): 0.47.2

Additional Context

Here is a reproduction repo: https://github.com/axieum/django-strawberry-example

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]

Hi @axieum ,

What is the use case for those namespaces? TBH I have seen someone mentioning something similar, but never saw that anywhere.

Also, is that a strawberry-django issue or a general strawberry issue?

[axieum]

Hi @bellini666 👋

It appears to just affect strawberry-django fields.

I was not able to reproduce when using pure strawberry fields.

There's a reproduction repository linked at the bottom of the issue which shows the strawberry-django namespacing issue.

Thanks,

[fabien-michel]

I've the same issue. A workaround seems to set create, update, delete... to something:

@strawberry.type
class Mutation:

    @strawberry.field(description="Mutate fruits")
    def fruits(self) -> FruitMutation:
        return FruitMutation(create=None, update=None, delete=None)

[axieum]

I've the same issue. A workaround seems to set create, update, delete... to something:

@strawberry.type
class Mutation:

    @strawberry.field(description="Mutate fruits")
    def fruits(self) -> FruitMutation:
        return FruitMutation(create=None, update=None, delete=None)

This looks to work for mutations 😄, but I can't get it to work for a query.

@strawberry.field(description="Query fruits")
def fruits(self) -> FruitQuery:
    return FruitQuery(all=None)

It raises a 'NoneType' object has no attribute 'all' suggesting that fruits is null. Did you have any luck with nesting queries?

[axieum]

Update; this works for nested queries.

@strawberry.field(description="Query fruits")
def fruits(self) -> FruitQuery:
    return FruitQuery(all=Fruit.__strawberry_django_definition__.model.objects)

I am unsure of the implications of providing a queryset here.

And this for nested mutations.

@strawberry.field(description="Mutate fruits")
def fruits(self) -> FruitMutation:
    return FruitMutation(create=None, update=None, delete=None)

Related to #580 (comment)