This release type improves support for strawberry.field in mypy, now we don't get `Attributes without a default cannot follow attributes with one` when using strawberry.field before a type without a default.
0.42.2
Not secure
-------------------
Bugfix to allow the use of `UNSET` as a default value for arguments.
python import strawberry from strawberry.arguments import UNSET, is_unset
strawberry.type class Query: strawberry.field def hello(self, name: Optional[str] = UNSET) -> str: if is_unset(name): return "Hi there" return "Hi {name}"
graphql type Query { hello(name: String): String! }
0.42.1
Not secure
-------------------
This release improves mypy support for strawberry.field
0.42.0
Not secure
-------------------
* Completely revamped how resolvers are created, stored, and managed by StrawberryField. Now instead of monkeypatching a `FieldDefinition` object onto the resolver function itself, all resolvers are wrapped inside of a `StrawberryResolver` object with the useful properties. * `arguments.get_arguments_from_resolver` is now the `StrawberryResolver.arguments` property * Added a test to cover a situation where a field is added to a StrawberryType manually using `dataclasses.field` but not annotated. This was previously uncaught.