Feature Request Type
- 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.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too