datamodel-code-generator

Version updated for https://github.com/koxudaxi/datamodel-code-generator to version 0.48.0.

  • This action is used across all versions by 2,491 repositories.

Go to the GitHub Marketplace to find the latest changes.

Action Summary

The datamodel-code-generator GitHub Action automates the generation of Python data models from various schema definitions, including OpenAPI 3, JSON Schema, GraphQL, and raw data formats like JSON, YAML, and CSV. It simplifies handling complex schemas, supports multiple output types such as Pydantic models, dataclasses, and TypedDict, and ensures type-safe, validated code for use with IDEs and type checkers. This tool streamlines schema-to-code workflows, saving time and reducing manual coding errors.

Release notes

Breaking Changes

Code Generation Changes

  • Custom class name generator now applied consistently during duplicate name resolution - Previously, when using custom_class_name_generator, the default PascalCase naming was incorrectly applied during duplicate name resolution. Now the custom generator is respected throughout, which may change generated class names. For example, a class name like nested_object_result with a custom generator f"Custom{name}" will now produce CustomNested_object_result instead of CustomNestedObjectResult. Users relying on the previous behavior should update their code to expect the new, correct class names. (#2757)

  • YAML 1.1 boolean keywords now preserved as strings in enums - Values like YES, NO, on, off, y, n that were previously converted to Python booleans are now preserved as their original string values. This fixes issues where string enum values were incorrectly converted but may change generated output for schemas that relied on the previous behavior. For example, a YAML enum with YES will now generate YES = 'YES' instead of being converted to True. (#2767)

Default Behavior Changes

  • YAML boolean parsing restricted to YAML 1.2 semantics - Only true, false, True, False, TRUE, FALSE are now recognized as boolean values. YAML 1.1 boolean aliases (yes, no, on, off, y, n, etc.) are no longer parsed as booleans and will be treated as strings. Non-lowercase forms (True, False, TRUE, FALSE) now emit a deprecation warning indicating future versions will only support lowercase true/false. (#2767)

What’s Changed

Full Changelog: https://github.com/koxudaxi/datamodel-code-generator/compare/0.47.0...0.48.0