build(deps): bump strawberry-graphql-django from 0.34.0 to 0.35.1

[dependabot[bot]]

Bumps strawberry-graphql-django from 0.34.0 to 0.35.1.

Release notes

Sourced from strawberry-graphql-django's releases.

Release 0.35.1

What's Changed

• fix: async with new filter API (assert queryset is wrong) by @​devkral in strawberry-graphql/strawberry-django#504

Full Changelog: https://github.com/strawberry-graphql/strawberry-django/compare/v0.35.0...v0.35.1

Release 0.35.0

🚀 Highlights (contains BREAKING CHANGES)

This release contains a major refactor of how filters and ordering works with this library (strawberry-graphql/strawberry-django#478).

Thank you very much for this excellent work @​Kitefiko 😊

Some distinctions between the new API and the old API:

Filtering

• The previously deprecated NOT filters with a leading n were removing, NOT is the only negation option from now on
• New DISTINCT: Boolean option to call .distinct() in the resulting QuerySet: https://strawberry-graphql.github.io/strawberry-django/guide/filters/#and-or-not-distinct
• Custom filters can be defined using a method with the @strawberry_django.filter_field decorator: https://strawberry-graphql.github.io/strawberry-django/guide/filters/#custom-filter-methods
• The default filter method can be overriden also by using a @strawberry_django.filter_field decorator: https://strawberry-graphql.github.io/strawberry-django/guide/filters/#overriding-the-default-filter-method
• Lookups have been separated into multiple types to make sure the API is not exposing an invalid lookup for a given attribute (e.g. trying to filter a BooleanField by __range): https://strawberry-graphql.github.io/strawberry-django/guide/filters/#generic-lookup-reference

IMPORTANT NOTE: If you find any issues and/or can't migrate your codebase yet, the old behaviour can still be achieved by setting USE_DEPRECATED_FILTERS=True in your django settings: https://strawberry-graphql.github.io/strawberry-django/guide/filters/#legacy-filtering

Also, make sure to report any issues you find with the new API.

Ordering

• It is now possible to define custom ordering methods: https://strawberry-graphql.github.io/strawberry-django/guide/ordering/#custom-order-methods
• The Ordering enum have 4 more options: ASC_NULLS_FIRST, ASC_NULLS_LAST, DESC_NULLS_FIRST and DESC_NULLS_LAST: https://strawberry-graphql.github.io/strawberry-django/guide/ordering/#ordering
• The default order method can now be overridden for the entire resolution: https://strawberry-graphql.github.io/strawberry-django/guide/ordering/#overriding-the-default-order-method

There are no breaking changes in the new ordering API, but please report any issues you find when using it.

New Contributors

• @​Kitefiko made their first contribution in strawberry-graphql/strawberry-django#478

Full Changelog: https://github.com/strawberry-graphql/strawberry-django/compare/v0.34.0...v0.35.0

Commits

• 425b75b chore(release): release 0.35.1
• 1086f6c fix: async with new filter API (assert queryset is wrong) (#504)
• 40a489b chore(release): release 0.35.0
• 4b3c874 chore: remove specific type ignore comments as they make the line too big
• c0cd67c Filter & Order ovehaul (#478)
• 5b520cb chore(deps): update dev dependencies
• 5bab771 [pre-commit.ci] pre-commit autoupdate (#503)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)