strawberry-django icon indicating copy to clipboard operation
strawberry-django copied to clipboard

Published 20 hours ago • verified publisher icon strawberry-graphql

Type Difficult to use, not ORM friendly

Open vt-rc opened this issue 1 year ago • 4 comments

Feature Request Type

  • [x] Core functionality
  • [ ] Alteration (enhancement/optimization) of existing feature(s)
  • [ ] New behavior

Description

I am trying to transit from graphene to strawberry, but it is very troublesome. I am surprise that the things that Graphene does so well are not adopted by strawberry.

My main issues are (1) Model based types doesn't auto discover relationship and just link up - in graphene, DjangoObjectType does this extremely well (2) Not very convenient to support custom orm fields - graphene also does this extremely well, with conversion (3) Not easy to add decorator on top of type, which are already wrapped in strawberry_django.type.

As Django developer, we are more ORM first, but Strawberry is probably too dataclass first, and leads to a lot of duplicate work and declaration. Ideally I should define ORM first and use it to generate type.

vt-rc avatar Oct 13 '24 08:10 vt-rc