Summary

• The Zones OAS spec ships a spec-level x-sdk-classname: CDNZones that openapi-generator threads to every emitted API file's class. When operations span multiple tags (zones-oas 1.3.0 introduces a Turnstile tag), the generator emits one file per tag — each declaring export class CDNZones — and the auto-generated barrel fails TS2308 on the duplicate. Any bump past zones-oas 1.2.0 is blocked.

  Concretely, generating zones-oas-v1=1.3.0 on main (without this fix):

  renderedTemplates/cdnApiProcessApis/apis/
  ├── DefaultApi.ts     # untagged zone ops    -> export class CDNZones
  ├── TurnstileApi.ts   # Turnstile-tagged ops -> export class CDNZones   <-- duplicate
  └── index.ts          # export * from './DefaultApi'
                        # export * from './TurnstileApi'                   <-- TS2308 here
  

  npm run compile fails with TS2308: Module './DefaultApi' has already exported a member named 'CDNZones' at apis/index.ts:2.

• Fix: pass --openapi-normalizer SET_TAGS_FOR_ALL_OPERATIONS=default to the openapi-generator invocation for the Zones spec only. That collapses every operation onto the default tag, so the generator emits a single DefaultApi.ts with all operations (Turnstile included) on one class — preserving the filename convention every other spec in the SDK already uses.

  Generating zones-oas-v1=1.3.0 on this branch (with the fix):

  renderedTemplates/cdnApiProcessApis/apis/
  ├── DefaultApi.ts     # every op incl. Turnstile -> export class CDNZones
  └── index.ts          # export * from './DefaultApi'
  

  npm run compile exits clean.

• Consumer surface is unchanged: import { CDNZones } from "commerce-sdk" resolves through the same barrel chain to the same class. At pinned 1.2.0 the emitted DefaultApi.ts, model files, and every downstream barrel are byte-identical to base.

Test plan

• Regression test at src/generate-oas.test.ts — proven red on base (TS2305: Module './generate-oas' has no exported member 'resolveGeneratorFlags', i.e. the test can't compile without the fix's carrier function) and green on fix (52 passing).
• npm run test:unit — 52 passing.
• npm run compile — clean typecheck.
• npm run lint — clean.
• Re-rendered locally at pinned zones-oas 1.2.0 with and without the fix — DefaultApi.ts, apis/index.ts, all 98 model files, models/index.ts, cdnApiProcessApis/index.ts, cdnApiProcessApis/runtime.ts, and the top-level renderedTemplates/index.ts are byte-identical between base and fix.
• Re-rendered locally at target zones-oas 1.3.0: single DefaultApi.ts, single export class CDNZones, all previous zone endpoints plus the 5 new Turnstile operations (createTurnstileWidget, deleteTurnstileWidget, getTurnstileWidget, etc.) on one class. Clean apis/index.ts barrel, no TS2308.

Reviewer manual smoke test

To reproduce the 1.3.0 generation locally on this branch:

# 1. Check out the branch
git fetch origin
git checkout ju/cdn-zones-classname-W-23234552
npm install

# 2. Bump the CDN Zones spec pin. Edit api-versions.txt line 5:
#      zones-oas-v1=1.2.0   ->   zones-oas-v1=1.3.0
#    Do NOT commit this edit — it's for local smoke only. The pin bump ships in
#    a separate release ticket.

# 3. Pull the 1.3.0 spec from Anypoint (needs Anypoint creds in your env):
export ANYPOINT_USERNAME=...
export ANYPOINT_PASSWORD=...
npm run updateApis

# 4. Regenerate + build.
npm run renderTemplates
npm run compile

Expected result:

• renderedTemplates/cdnApiProcessApis/apis/ contains exactly one API file, DefaultApi.ts, with export class CDNZones extends BaseClient. No TurnstileApi.ts, no duplicate class.
• DefaultApi.ts has all pre-existing zone endpoints plus the 5 new Turnstile operations (createTurnstileWidget, deleteTurnstileWidget, getTurnstileWidget, getTurnstileWidgets, updateTurnstileWidget).
• 6 new TurnstileWidget* model files under renderedTemplates/cdnApiProcessApis/models/.
• npm run compile exits 0 (no TS2308 on the barrel).

Sanity check on main first (optional): repeat steps 2–4 on main and npm run compile will fail with TS2308: Module './DefaultApi' has already exported a member named 'CDNZones' at renderedTemplates/cdnApiProcessApis/apis/index.ts:2 — this is the failure this PR resolves.

To restore local state after smoke: git checkout -- api-versions.txt && rm -rf apis/zones-oas-1.3.0 renderedTemplates.

Follow-ups

• The api-versions.txt bump of zones-oas-v1 from 1.2.0 to 1.3.0 belongs in a separate release ticket per the ticket's AC.
• src/generate-oas.ts:58 — resolveApiName's "CDN API - Process APIs OAS" branch is dead (no shipping spec uses that name); the current name is "Zones OAS", handled at line 82. Chore ticket to clean up.
• The three parallel per-spec switches (resolveApiName, resolveDirectoryName, resolveGeneratorFlags) could collapse into one data-driven config table. Separate Refactor ticket.
• The mustache template at templatesOas/apis.endpoint.mustache:242 emits const pathParams = {} without a type annotation. VS Code's default noImplicitAny lights up every generated DefaultApi.ts in the repo with editor squiggles — cosmetic only, the repo tsconfig.json compiles cleanly. Chore ticket to add Record<string, unknown> to the mustache emit.

Ticket

W-23234552