Naming Conventions

AutoSDK transforms OpenAPI names into idiomatic C# identifiers. This page explains the naming strategies and how to control them.

Type Naming

OpenAPI schema names are converted to PascalCase C# type names:

Nested Types

When schemas contain inline objects, AutoSDK has two strategies controlled by AutoSDK_NamingConvention:

ConcatNames (default) — Concatenates parent and property names:

Pet:
  properties:
    owner:
      type: object
      properties:
        name:
          type: string

Generates: PetOwner class

InnerClasses — Uses nested C# classes:

Generates: Pet.Owner class

Collision Resolution

When two schemas would produce the same C# name, AutoSDK appends numeric suffixes:

• Pet (from pet)
• Pet2 (from Pet in a different context)

Method Naming

Three conventions are available via --methodNamingConvention:

SimpleOperationId (Default)

Uses the operationId from the spec, PascalCased:

MethodAndPath

Combines HTTP method and URL path:

OperationIdWithDots

Preserves dots as namespace separators for APIs that use dotted operation IDs:

Fallback

If an operation has no operationId, AutoSDK falls back to MethodAndPath regardless of the configured convention. Control this with --methodNamingConventionFallback.

Enum Naming

Enum members are PascalCased from their string values:

CLS-Compliant Prefix

Enum values starting with a digit get a configurable prefix (default: x):

Configure with AutoSDK_ClsCompliantEnumPrefix.

x-enum-varnames

Override generated names entirely:

Status:
  type: string
  enum: ["a", "b", "c"]
  x-enum-varnames: ["Active", "Blocked", "Closed"]

Parameter Naming

Operation parameters are camelCased for C# method parameters: