Way to allow the default strawberry django field to accept UUID as an input

[12tqian]

I am making a query with the following structure:

@strawberry.type
class ObjectQuery:
    object: ObjectNode = strawberry.django.field()

However, the input for this requires a type of pk: ID. Is it possible to change this to be of type pk: UUID? My current solution for this is just to write a generic custom resolver.

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.

[patrick91]

@bellini666 do you have any ideas for an API for this use case?

Just thinking out loud, plain strawberry supports this:

def a_resolver(id: UUID) -> ObjectNode:
   ...

@strawberry.type
class ObjectQuery:
    object: ObjectNode = strawberry.field(resolver=a_resolver)

we could maybe have a way to fetch the params from a stub function:

def a_resolver(id: UUID) -> ObjectNode:
   ...

@strawberry.type
class ObjectQuery:
    object: ObjectNode = strawberry.django.field(params_from=a_resolver)

but sounds like it is a bit of work, but it might be useful for additional filtering.

or maybe we can pass a params_override:

@strawberry.type
class ObjectQuery:
    object: ObjectNode = strawberry.django.field(params_override={"pk": UUID})

[bellini666]

Hey @patrick91 ,

Although I like your idea, I think we can probably do even better.

That pk gets created in here. We can probably just change the strawberry.ID to retrieve it from field_type_map using the pk field from django. That way it will use the correct type for the model's pk (e.g. strawberry.ID for AutoField, UUID for UUIDField, etc)

What do you think?

[klowe0100]

Hey @patrick91 ,

Although I like your idea, I think we can probably do even better.

That pk gets created in here. We can probably just change the strawberry.ID to retrieve it from field_type_map using the pk field from django. That way it will use the correct type for the model's pk (e.g. strawberry.ID for AutoField, UUID for UUIDField, etc)

What do you think?

This approach makes a lot of sense to me and follows strawberry-django's theme of auto sensing field types from the django model.