koxudaxi/datamodel-code-generator - CodSpeed

datamodel-code-generator

Blog Docs Changelog

Performance History

Latest Results

Keep additionalProperties value constraints in annotated output parse_item promotes a constrained primitive to a constrained sub-type (so a Meta/Field can carry ge/le/pattern/etc.) only when a parent is passed. parse_list_item passes parent, so a constrained array item keeps its constraint, but the additionalProperties branch of parse_item did not, so a constrained dict value silently dropped it whenever field_constraints is on (msgspec, and pydantic_v2/dataclasses with --use-annotated). So `{"additionalProperties": {"type": "integer", "minimum": 1, "maximum": 9}}` generated `dict[str, int]` in those modes, while the sibling array item and the pydantic-inline output (dict[str, conint(ge=1, le=9)]) both kept the bound. Pass parent=item to that call so the dict value is promoted the same way the list item is. pydantic_v2 inline output is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Andrew Chen <48723787+chuenchen309@users.noreply.github.com>

chuenchen309:fix/additional-properties-value-constraints

11 hours ago

Rename a msgspec field named "field" to avoid shadowing the field import msgspec models emit `from msgspec import ... field` and call `field(...)` for aliases, defaults, etc. A schema property named "field" was rendered as a class attribute `field`, shadowing that import, so any later `field(...)` call raised `TypeError: 'msgspec._core.Field' object is not callable` and the generated module could not be imported. Add a msgspec-specific field-name resolver (mirroring the Pydantic one) that renames a "field" property to `field_` with a `name="field"` alias, and route msgspec Structs to it via field_name_model_type. Adds a regression test that generates and imports the model. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

chuenchen309:fix/msgspec-field-name-shadow

12 hours ago

docs: update release benchmark data

docs/release-benchmark-0.69.0

12 hours ago

docs: update CHANGELOG.md for 0.69.0

docs/changelog-0.69.0

12 hours ago

Fix empty ("") property name dropping its alias (#3612) * Fix empty ("") property name dropping its alias A JSON Schema property named "" is legal (and may be required). The resolver correctly maps it to the field name `field_` with alias `""`, but the rendering layer decided whether to emit the alias with a truthiness check (`if self.alias:` / `or self.alias`). The empty string is falsy, so `alias=''` was dropped and the generated model expected a key literally named `field_` — `Model.model_validate({'': 'x'})` then failed with "field_ Field required". The tool already handles the adjacent cases (`#` -> alias='#', a leading digit -> alias='123name'); only the empty name silently lost its alias. Test the presence of the alias with `is not None` instead of truthiness, in pydantic and the identical msgspec branch. A normal field still has `alias is None`, so no spurious alias is added. * Preserve empty property names across generation paths * Make TypedDict runtime test Python 3.10 compatible * Cover empty-name fallback branches --------- Co-authored-by: Koudai Aono <koxudaxi@gmail.com>

main

12 hours ago

Cover empty-name fallback branches

chuenchen309:fix/empty-property-name-alias

13 hours ago

Make TypedDict runtime test Python 3.10 compatible

chuenchen309:fix/empty-property-name-alias

13 hours ago

Preserve empty property names across generation paths

chuenchen309:fix/empty-property-name-alias

13 hours ago

Latest Branches

-34%

Keep additionalProperties value constraints in annotated output#3616

12 hours ago

4f78a6b

chuenchen309:fix/additional-properties-value-constraints

+1%

Rename a msgspec field named "field" to avoid shadowing the field import#3615

12 hours ago

b6b19d4

chuenchen309:fix/msgspec-field-name-shadow

-32%

Update release benchmark data#3614

12 hours ago

931399e

docs/release-benchmark-0.69.0

© 2026 CodSpeed Technology

Home Terms Privacy Docs