input_mutation: TypeError: MutateContentInput fields cannot be resolved

[devkral]

input_mutation: TypeError: MutateContentInput fields cannot be resolved

[bellini666]

Hey @devkral ,

Is that issue happening with the v3 release?

Could you provide me a step by step on how to reproduce that traceback using your project?

[devkral]

Steps to reproduce

• setup secretgraph (cloning repo and install the virtual environment with poetry install)
• poetry run ./manage.py export_schema (here happens the crash)

[bellini666]

@devkral

Hrm, I could reproduce the issue in your repo, but I'm not really sure what is happening there. It seems that the argument is loosing its namespace in the StrawberryAnnotation, but I don't know what is causing it. Maybe it is some weird interaction based on the fact that you do some kind of nested mutation resolving (first time seeing something like this =P).

Also, the input mutation is now using the strawberry's InputMutationExtension, so I think the issue is probably there.

Could you try to create a minimal contained reproduction example for this? It would be nice to test if the minimal reproduction example happens only with strawberry-django-plus or if it does happen when when using the InputMutationExtension directly.

[devkral]

thanks for the hint, did test it against InputMutationExtension. it fails with only

 updateOrCreateContent: ContentMutation = gql.mutation(
        resolver=mutate_content,
        extensions=[InputMutationExtension()],
        handle_django_errors=False,
    )

for a poc just remove all input_mutation except one in the secretgraph/server/schema/schema.py and modify it.

The command works if all input_mutations are removed

[devkral]

I think it is a bug in InputMutationExtension

[devkral]

It could be related to:
strawberry-graphql/strawberry#2864

[devkral]

I could fix this error by removing from __future__ import annotations. I provided a POC as test in strawberry:
strawberry-graphql/strawberry#2868

[bellini666]

@devkral oh, that's nice! I'll take a look at it soon to try to understand what might be going on

[devkral]

fixed (PR merged and tests don't fail anymore).