Option recommendations (experimental; full mode; rules 2026-10-19)

Schema  OpenAPI 3.1.0 (OpenAPI scopes: schemas)
  components                       6, 2 operations
  inline objects / enums           12 / 6, nesting depth 1
  shared property names            4 (status x3, owner x3, state x2, total x2)
  inline names = component names   0
  repeated inline objects / enums  10 of 2 shapes / 0 of 0 value sets
  titled components                0: 0 shared titles (none), 0 equal another key, 0 equal their own key
  inline titles                    5 objects, most repeated 5 (User x5)
  unions                           1 oneOf/anyOf, 0 with a discriminator, 2 inline variants
  union branch tags                2 tagged, 0 single required key, 0 tagged only through allOf $ref, 0 copy their parent
  component keys                   PascalCase (4 of 6); 2 dotted in 2 namespaces
  constraint keywords              uniqueItems 0, patternProperties 0 (0 beyond a typed map), multipleOf 0, OpenAPI 3.0 nullable 0, boolean exclusive bounds 0
  formats                          0 (none), decimal 0; int32/int64 0, ranges not enforced
  integer/number/boolean schemas   5

Start from  --preset standard-py314-20261027

Add (5 options)
  --enum-field-as-literal all   [enums.inline-value-sets-as-literal]
      Most enums are inline value sets of one property (inline enums: 6 of 6). As Enum classes they
      add one class name each, the longest and most numbered names; Literal types keep the values
      without a class.
      measured: GitHub REST API description: 1872 -> 1538 types, names over 40 characters 370 -> 227
      measured: Stripe API description: problem names 348 -> 158
      measured: SchemaStore workflow schema: Type1 to Type19 disappear
      trial: recommended - naming-strategy - enum-shape -> recommended - naming-strategy: classes 15
      -> 9, problem names 3 -> 0; 0 of 9 classes matched by schema location renamed (0 only
      renumbered), 6 removed, 0 added
  --reuse-model --collapse-reuse-models   [reuse.identical-inline-shapes]
      The schema repeats shapes (inline objects repeating a shape: 10, in 2 shapes; inline enums
      repeating a value set: 0, in 0 sets; union branches that only constrain their parent's
      properties, which generation copies per branch: 0). Reuse emits each shape once, and collapse
      refers to it instead of an empty subclass.
      measured: GitHub REST API description: 3263 -> 1872 types, numbered names 1774 -> 663
      measured: Stripe API description: 2512 -> 2022 types
      measured: SchemaStore workflow schema: the step branches' copies With1 to With11 became one
      With1
      trial: recommended - naming-strategy - reuse -> recommended - naming-strategy: classes 14 ->
      9, problem names 0 -> 0; 0 of 9 classes matched by schema location renamed (0 only
      renumbered), 5 removed, 0 added
  --no-treat-dot-as-module   [dotted-keys.flat-when-namespaces-cycle]
      Dotted keys (2, in 2 namespaces) reference each other in cycles (namespace groups: 1). As
      modules, cycle members move to _internal.py, where same-named classes of different namespaces
      get _1 suffixes; flat names avoid that.
      measured: Stripe API description: Card_1 and Customer_1 disappear, problem names 158 -> 153
      measured: Kubernetes apps/v1: no cycles, so modules stay (median name length 16 as modules, 32
      flat)
      trial: recommended - naming-strategy - dotted-keys -> recommended - naming-strategy: classes
      12 -> 9, problem names 0 -> 0; 2 of 9 classes matched by schema location renamed (0 only
      renumbered), 3 removed, 0 added, e.g.
        Invoice -> BillingInvoice   at components/schemas/billing.Invoice
        Shipment -> ShippingShipment   at components/schemas/shipping.Shipment
  --use-tag-as-union-variant-name   [unions.name-variants-after-tags]
      Inline oneOf/anyOf branches can be named after a tag or key (branches with a tag value no
      sibling shares: 2; objects with one required key: 0); otherwise they are named after their
      parent and a number.
      measured: OpenAI API description (59 tagged, 10 key branches): preset 797 -> 759 problem names
      (ThreadStreamEvent1 -> ThreadStreamEventThreadCreated)
      measured: GitHub REST API description (1 tagged, 4 key branches): preset 1808 -> 1805
      (Changes23 -> ChangesBody)
      measured: SchemaStore workflow schema (5 tagged): 49 -> 44 (WorkflowDispatchInput1 to 5 ->
      WorkflowDispatchInputString, Boolean, ...)
      measured: with full-path on the GitHub and OpenAI descriptions: no change in problem names;
      schemas without tagged or key branches: no change
      trial: recommended - naming-strategy - union-variant-names -> recommended - naming-strategy:
      classes 9 -> 9, problem names 2 -> 0; 2 of 9 classes matched by schema location renamed (0
      only renumbered), 0 removed, 0 added, e.g.
        Payment1 -> PaymentCard   at components/schemas/Payment > oneOf 0
        Payment2 -> PaymentBank   at components/schemas/Payment > oneOf 1

Left out after the trial (the rules recommend these)
  --naming-strategy full-path   [naming.qualify-shared-inline-names]
      Inline schemas under different parents share property names (names: 4, e.g. status x3, owner
      x3, state x2, total x2; inline names equal to a component name: 0). Numbered names (Status,
      Status1) depend on parse order and shift when the schema grows; full-path names each inline
      model after its parent.
      measured: GitHub REST API description: numbered names 663 -> 53; locations renamed between two
      versions 17% -> 0.0%
      measured: Petstore: Status and Status1 became OrderStatus and PetStatus
      measured: Stripe API description: the expandable ID string of charge no longer displaces the
      charge component (ChargeModel)
      measured: SchemaStore workflow and tsconfig schemas: full-path doubled or lengthened names and
      lost
      trial: recommended - naming-strategy -> recommended: classes 9 -> 9, problem names 0 -> 2; 4
      of 9 classes matched by schema location renamed (0 only renumbered), 0 removed, 0 added, e.g.
        Total -> OrderTotal   at components/schemas/Order > total
        PaymentCard -> PaymentPaymentCard   at components/schemas/Payment > oneOf 0
        PaymentBank -> PaymentPaymentBank   at components/schemas/Payment > oneOf 1

Optional (policy; not in the command)
  --strict-types int float bool   [policy.strict-scalar-types]
      Pydantic validates in lax mode, which coerces input into the 5 integer, number and boolean
      schemas: it accepts the string "5" and true as integers, "1.5" as a number, and "true" or 1 as
      booleans. Strict types reject such input. Whether to accept it depends on the project's
      clients, not on the schema; strict int also rejects 5.0, which JSON Schema counts as an
      integer, so leave int out to accept it.
      measured: 11 JSON documents for integer, number, boolean and string properties, 6 of them
      invalid: lax mode accepted 5 invalid ones; with int float bool, 0 accepted and 1 valid one
      rejected (5.0 as an integer); with float bool, 2 accepted ("5" and true as integers) and none
      rejected

Not recommended
  --use-title-as-name   [titles.keys-when-titles-collide]
      Titles do not identify the schemas (shared titles: 0, covering 0 components; titles equal to
      another component's key: 0; most repeated inline title: 5; titles that repeat their own key: 0
      of 0). Titles as class names would number components, or rename them when a title changes;
      names from the keys avoid both.
      measured: GitHub REST API description: 53 shared component titles numbered components
      (page-deployment became GitHubPages1, Actor2)
      measured: OpenAI API description: 503 problem names with titles off, 544 with titles on
      measured: Stripe API description: 17% of component titles changed in four months; class names
      from keys renamed 0.0% of locations

Trial  12 candidates generated in memory without formatting; nothing written
  candidate                                            classes   problems  numbered  long  doubled  displaced  median  unconstrained
  current                                                   22  5 (22.7%)         5     0        0          0       6              0
  preset                                                    22  5 (22.7%)         5     0        0          0       6              0
  recommended                                                9  2 (22.2%)         0     0        2          0      10              0
  recommended - naming-strategy                              9   0 (0.0%)         0     0        0          0       5              0   selected
  recommended - enum-shape                                  15  2 (13.3%)         0     0        2          0      11              0
  recommended - reuse                                       17  2 (11.8%)         0     0        2          0      14              0
  recommended - dotted-keys                                 12  2 (16.7%)         0     0        2          0       7              0
  recommended - union-variant-names                          9  2 (22.2%)         1     0        2          0      10              0
  recommended - naming-strategy - enum-shape                15  3 (20.0%)         3     0        0          0       6              0
  recommended - naming-strategy - reuse                     14   0 (0.0%)         0     0        0          0       5              0
  recommended - naming-strategy - dotted-keys               12   0 (0.0%)         0     0        0          0       5              0
  recommended - naming-strategy - union-variant-names        9  2 (22.2%)         2     0        0          0       5              0
  current: the configuration as set, without the preset; never selected
  the last 4 rows: the selected configuration without or with one option, to measure each option on
  it; never selected
  unconstrained: fields that dcg warns it generates without some of their constraints

Changes from the current configuration (current -> recommended - naming-strategy)
  4 of 9 classes matched by schema location renamed (0 only renumbered), 13 removed, 0 added, e.g.
    Payment1 -> PaymentCard   at components/schemas/Payment > oneOf 0
    Payment2 -> PaymentBank   at components/schemas/Payment > oneOf 1
    Invoice -> BillingInvoice   at components/schemas/billing.Invoice

Notes
  - The rules were calibrated on the 20261017 presets.

Command
  datamodel-codegen

pyproject.toml: keys to add or change
  [tool.datamodel-codegen]
  collapse-reuse-models = true
  enum-field-as-literal = "all"
  preset = "standard-py314-20261027"
  reuse-model = true
  treat-dot-as-module = false
  use-tag-as-union-variant-name = true
