Release 0.46.1

What's Changed

• fix: Fix and test optimizer with polymorphic relay node by @stygmate in #570
• fix: Fix nested pagination/filtering/ordering not working when "only optimization" is disabled by @aprams in #569

Full Changelog: v0.46.0...v0.46.1

Release 0.46.0

What's Changed

• feat: Add support for auto mapping of ArrayFields by @bellini666 in #567
• fix: Set files early on mutations to allow clean methods to validate them by @bellini666 in #566
• fix: Make sure the optimizer calls the type's get_queryset for nested lists/connections by @bellini666 in #568

Full Changelog: v0.45.0...v0.46.0

Release 0.45.0

What's Changed

• Generated fields type resolution by @Mapiarz in #565

Full Changelog: v0.44.2...v0.45.0

Release 0.44.2

What's Changed

• docs: wrong typo on filter on fruitfilter by @OdysseyJ in #555
• docs: Remove officially unmaintained project by @Eraldo in #557
• test: Add some tests to ensure Interfaces can be properly optimized by @bellini666 in #554
• fix: Extract interface definition in optimizer to fix django-polymorphic by @ManiacMaxo in #556

New Contributors

• @OdysseyJ made their first contribution in #555

Full Changelog: v0.44.1...v0.44.2

Release 0.44.1

What's Changed

• fix: fix optimized nested connections failing to access totalCount by @bellini666 and @Eraldo in #553

Full Changelog: v0.44.0...v0.44.1

Release 0.44.0

What's Changed

• feat: Nested optimization for lists and connections by @bellini666 in #540

This releases finally enables the highly anticipated nested optimization for lists and connections 🚀

What does that mean? Remember that when trying to retrieve a relation list inside another type and also trying to filter/order/paginate, that would cause n+1 issues because it would force the prefetched list to be thrown away? Well, not anymore after this release! 😊

In case you find any issues with this, please let us know by registering an issue with as much information as possible on how to reproduce the issue.

Note that even though this is enabled by default, nested optimizations can be disabled by passing enabled_nested_relations_prefetch=False when initializing the optimizer extensions.

• Dropped support for Django versions earlier than 4.2

The nested optimization feature required features only available on Django 4.2+.

To be able to implement it, and also considering that django itself recommended dropping support for those versions, from now on this lib requires Django 4.2+

Full Changelog: v0.43.0...v0.44.0

Release 0.43.0

What's Changed

• Added export-schema command to Docs by @Ckk3 in #546
• fix: Fix specialized connection aliases missing filters/ordering by @bellini666 in #547

NOTE: Even though this only contains a bug fix, I decided to do a minor release because the fix is bumping the minimum required version of strawberry-graphql itself to 0.234.2.

New Contributors

• @Ckk3 made their first contribution in #546

Full Changelog: v0.42.0...v0.43.0

Release 0.42.0

What's Changed

• refactor: Use graphql-core's collect_sub_fields instead of our own implementation by @bellini666 in #537

Full Changelog: v0.41.1...v0.42.0

Release 0.41.1

What's changed

• fix: Move Info out of the TYPE_CHECKING block to prevent a warning (4e8c458)

Full Changelog: v0.41.0...v0.41.1

Release 0.41.0

What's Changed

• docs: Fix typo by @Eraldo in #531
• feat: Add setting DEFAULT_PK_FIELD_NAME by @noamsto in #446
• fix: Fix AttributeError when using optimizer and prefetch_related by @jacobwegner in #533

New Contributors

• @Eraldo made their first contribution in #531
• @noamsto made their first contribution in #446
• @jacobwegner made their first contribution in #533

Full Changelog: v0.40.0...v0.41.0