strawberry-graphql/strawberry - CodSpeed

strawberry-graphql

strawberry

Blog Docs Changelog

Performance History

Latest Results

Support strawberry.Maybe on pydantic inputs (#4795)

main

5 minutes ago

Make Maybe defaults part of the pydantic schema The decorator gave Maybe fields a None default, but only the FieldInfo: the core schema still had the field as required under any field validator, like field_validator("*"), and pydantic validated the default after a model_rebuild() with validate_default, or on a subclass. The decorator now sets validate_default=False and rebuilds the schema. An after or plain field_validator naming a Maybe field is an error, as it gets the Some or replaces the validation of the Maybe.

pydantic-maybe

22 minutes ago

Check the Maybe model signature structurally The snapshot embedded the StringConstraints repr, which differs between pydantic 2.11 and 2.12 (ascii_only), so it failed on the minimum version session.

pydantic-maybe

40 minutes ago

Support strawberry.Maybe on pydantic inputs `Maybe` gets a pydantic core schema, through a hook that defers to the integration: a value is validated as `T` and wrapped in `Some`, the field defaults to `None` without validating it, and `model_dump()` gives the value inside the `Some`, so `model_dump(exclude_unset=True)` only has the fields the client sent. Strawberry passes the values as they are, recursing into nested inputs and lists, and nulls go through `convert_argument`, so `Maybe[T]` rejects them like on `@strawberry.input`. `MaybeFieldError` now covers what the integration doesn't support: `Maybe` on output types, defaults other than `None`, pydantic metadata outside the `Maybe`, which would apply to the `Some`, and `validate_default` on an explicit `None`.

pydantic-maybe

46 minutes ago

fix(codegen): stop double-wrapping nullable Maybe input fields (#4759)

main

2 hours ago

🤖 Release 0.340.0 This release adds a `sort_schema` option to `StrawberryConfig`. When enabled, the GraphQL schema is sorted lexicographically. This affects both introspection queries and exported schemas, making them easier to read and diff. [skip ci]

main

8 hours ago

🤖 Release 0.340.0 This release adds a `sort_schema` option to `StrawberryConfig`. When enabled, the GraphQL schema is sorted lexicographically. This affects both introspection queries and exported schemas, making them easier to read and diff. [skip ci]

main

1 day ago

feat: add sort_schema config option to sort GraphQL schema lexicographically (#4733) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

main

2 days ago

Latest Branches

0%

Support strawberry.Maybe on pydantic inputs#4795

25 minutes ago

fa7f570

pydantic-maybe

0%

feat: add sort_schema config option to sort GraphQL schema lexicographically#4733

14 days ago

f5e7b9d

lilacrainlog-art:feat/issue-3149-sort-schema

-31%

Make query codegen type ordering consistent across Python versions#4776

6 days ago

b3602f3

linevych:fix/deterministic-codegen-order

© 2026 CodSpeed Technology

Home Terms Privacy Docs