Strawberry-graphql

Latest version: v0.229.1

Safety actively analyzes 629765 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 90 of 119

0.53.0

Not secure
-------------------

* `FieldDefinition` has been absorbed into `StrawberryField` and now no longer exists.

* `FieldDefinition.origin_name` and `FieldDefinition.name` have been replaced with
`StrawberryField.python_name` and `StrawberryField.graphql_name`. This should help
alleviate some backend confusion about which should be used for certain situations.

* `strawberry.types.type_resolver.resolve_type` has been split into
`resolve_type_argument` and `_resolve_type` (for arguments) until `StrawberryType` is
implemented to combine them back together. This was done to reduce the scope of this
PR and defer changing `ArgumentDefinition` (future `StrawberryArgument`) until a
different PR.

> Note: The constructor signature for `StrawberryField` has `type_` as an argument
> instead of `type` as was the case for `FieldDefinition`. This is done to prevent
> shadowing of builtins.

> Note: `StrawberryField.name` still exists because of the way dataclass `Field`s
work, but is an alias for `StrawberryField.python_name`.

0.52.1

Not secure
-------------------

Include `field_nodes` in Strawberry info object.

0.52.0

Not secure
-------------------

Change `get_context` to be async for sanic integration

0.51.1

Not secure
-------------------

Configures GraphiQL to attach CSRF cookies as request headers sent to the GQL server.

0.51.0

Not secure
-------------------

Expose Strawberry Info object instead of GraphQLResolveInfo in resolvers

0.50.3

Not secure
-------------------

Django 3.2 support

Page 90 of 119

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.