There are a lot of features on strawberry-django-plus that not only are usually requested by the community, they really would benefit this project.
I would like to make this a meta issue for discussing which features should be ported.
Here is a list of features that I think should be ported, linked to their respective issues:
[x] Better typing for exposed api (#136)
[x] Improve attribute resolving by avoiding sync_to_async overhead when the value is already cached (#137)
[x] Query optimizer that automatically adds select_related/prefetch_related/only optimizations to querysets (#75)
[x] Support for model property(#134)
[x] Better mutations handling, with support for nested inputs (#133 and #67)
Those here needs further discussion to know if they are interesting for this project or not, since they are integrations with 3rd party libs:
[x] Built-in support for django-debug-toolbar (#138)
[x] Built-in support for using django's TextChoices as enums. This is implemented in strawberry-django-plus with the help of django-choices-field (#65 and #66)
Those would be better ported with support on strawberry first:
There are a lot of features on strawberry-django-plus that not only are usually requested by the community, they really would benefit this project.
I would like to make this a meta issue for discussing which features should be ported.
Here is a list of features that I think should be ported, linked to their respective issues:
select_related
/prefetch_related
/only
optimizations to querysets (#75)property
(#134)Those here needs further discussion to know if they are interesting for this project or not, since they are integrations with 3rd party libs:
TextChoices
as enums. This is implemented instrawberry-django-plus
with the help of django-choices-field (#65 and #66)Those would be better ported with support on
strawberry
first:Upvote & Fund