A. Coady
A. Coady
Looks like this is already done in recent versions.
Partial results with errors, as documented in [Error Result Format](https://spec.graphql.org/draft/#sec-Errors.Error-Result-Format), is already supported. The key is the field with the error must be nullable. The original post is more specifically...
It can be done with an empty dict/object. The received value will still be the default input type. ```python def example(self, data: InputData = {}) -> str: ```
The issue is `param` requires wrapping all the argument values, so it's impossible for this to work with multiple "zipped" values. Because the point of this library is to allow...
Released [v1.6](https://github.com/coady/pytest-parametrized/releases/tag/v1.6).
This has come up before; I think it's a mypy limitation. AFAICT, static checkers special-case symbols like `overload` and `singledispatch`. For example, replacing ```python singledispatch = multimethod @singledispatch ... ````...
Try adding `from functools import singledispatch`.
I don't think this can be supported (and still be compliant with the spec). GraphQL defaults are statically in the schema. `strawberry export-schema ...`: ```graphql type Mutation { update1(fields: MyInputType!):...
> @coady sorry to ping you again, but do you use default_factory for defaults in the schema level? 😊 what's your use case exactly? The only use I'm aware of...
The regression occurred in 0dcf23d, which changed how extensions are created. It appears a new extension instance is created on each request, `resolve` is called on the old instance, then...