Update strawberry-graphql[channels] requirement from <=0.177.0 to <=0.178.0 in /caster-back

[dependabot]

Updates the requirements on strawberry-graphql[channels] to permit the latest version.

Release notes

Sourced from strawberry-graphql[channels]'s releases.

🍓 0.178.0

This release introduces the new should_ignore argument to the QueryDepthLimiter extension that provides a more general and more verbose way of specifying the rules by which a query's depth should be limited.

The should_ignore argument should be a function that accepts a single argument of type IgnoreContext. The IgnoreContext class has the following attributes:

• field_name of type str: the name of the field to be compared against
• field_args of type strawberry.extensions.query_depth_limiter.FieldArgumentsType: the arguments of the field to be compared against
• query of type graphql.language.Node: the query string
• context of type graphql.validation.ValidationContext: the context passed to the query and returns True if the field should be ignored and False otherwise. This argument is injected, regardless of name, by the QueryDepthLimiter class and should not be passed by the user.

Instead, the user should write business logic to determine whether a field should be ignored or not by the attributes of the IgnoreContext class.

For example, the following query:

"""
    query {
      matt: user(name: "matt") {
        email
      }
      andy: user(name: "andy") {
        email
        address {
          city
        }
        pets {
          name
          owner {
            name
          }
        }
      }
    }
"""

can have its depth limited by the following should_ignore:

from strawberry.extensions import IgnoreContext
def should_ignore(ignore: IgnoreContext):
return ignore.field_args.get("name") == "matt"
query_depth_limiter = QueryDepthLimiter(should_ignore=should_ignore)

so that it effectively becomes:

... (truncated)

Changelog

Sourced from strawberry-graphql[channels]'s changelog.

0.178.0 - 2023-05-22

This release introduces the new should_ignore argument to the QueryDepthLimiter extension that provides a more general and more verbose way of specifying the rules by which a query's depth should be limited.

The should_ignore argument should be a function that accepts a single argument of type IgnoreContext. The IgnoreContext class has the following attributes:

• field_name of type str: the name of the field to be compared against
• field_args of type strawberry.extensions.query_depth_limiter.FieldArgumentsType: the arguments of the field to be compared against
• query of type graphql.language.Node: the query string
• context of type graphql.validation.ValidationContext: the context passed to the query and returns True if the field should be ignored and False otherwise. This argument is injected, regardless of name, by the QueryDepthLimiter class and should not be passed by the user.

Instead, the user should write business logic to determine whether a field should be ignored or not by the attributes of the IgnoreContext class.

For example, the following query:

"""
    query {
      matt: user(name: "matt") {
        email
      }
      andy: user(name: "andy") {
        email
        address {
          city
        }
        pets {
          name
          owner {
            name
          }
        }
      }
    }
"""

can have its depth limited by the following should_ignore:

from strawberry.extensions import IgnoreContext
def should_ignore(ignore: IgnoreContext):
return ignore.field_args.get("name") == "matt"
query_depth_limiter = QueryDepthLimiter(should_ignore=should_ignore)
</tr></table>

... (truncated)

Commits

• 4519c39 Release 🍓 0.178.0
• c2d50c0 Extend query depth limiter allowing for more detailed rules (#2505)
• c443d9c Release 🍓 0.177.3
• f0ddaa2 Allow additional tags in DatadogTracingExtension (#2773)
• efc684a Release 🍓 0.177.2
• aee5ec9 fix: fix optional scalars using the "or" notation on python 3.10 (#2774)
• 51eb183 Ann003 (#2767)
• a621868 Docs update
• 29152f4 Release 🍓 0.177.1
• 2c4c57c Add support for IntEnum (#2761)
• Additional commits viewable 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 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)

[dependabot]

Superseded by #443.