fix(http): type context parameters and headers with concrete generated models

[ALagoni97]

Problem

When generating a TypeScript HTTP fetch client, the generated context interface discarded the fully-typed parameter class and headers model that are already generated. Instead of the concrete types, it emitted structural stubs:

export interface GetV2TransactionsContext extends HttpClientContext {
  parameters: { getChannelWithParameters: (path: string) => string };
  requestHeaders?: { marshal: () => string };
}

So a consumer calling getV2Transactions(context) got no type support on context.parameters (the actual query/path params like skip, take, search, referenceId) or context.requestHeaders.

Fix

generateContextInterface (in http/client.ts) only received a hasParameters: boolean and never saw the concrete class names — even though they were already in hand (channelParameters.type). The headers model wasn't threaded into the renderer at all.

• Thread channelParameters.type / channelHeaders.type into the context interface, mirroring the existing EventSource protocol.
• Plumb the headers model through http/index.ts → renderHttpFetchClient (added channelHeaders to RenderHttpParameters).

Result:

export interface GetGetUserItemContext extends HttpClientContext {
  parameters: UserItemsParameters;
  requestHeaders?: ItemRequestHeaders;
}

The concrete parameter class still exposes getChannelWithParameters, so buildUrlWithParameters(...) in the function body is unaffected. Operations without a typed headers model keep the structural { marshal: () => string } fallback.

Verification

• npm run typecheck passes.
• Regenerated the committed runtime output (test/runtime/typescript/src/request-reply/channels/http_client.ts) — context interfaces now reference UserItemsParameters / ItemRequestHeaders, matching what the parameters-headers.spec.ts runtime spec already imports and constructs.
• Sanity-checked against the openapi-http-client example: parameters now resolves to the concrete generated params class.

Note: npm run prepare:pr could not be run to completion locally because ESLint 8's extensionless .eslintrc loader fails under Node 25 (pre-existing, reproduces on a clean checkout, unrelated to this diff). Please run the full quality gate in CI / on a Node 22 environment.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
the-codegen-project	Ready	Preview, Comment	Jul 13, 2026 5:08pm
the-codegen-project-mcp	Ready	Preview, Comment	Jul 13, 2026 5:08pm

[jonaslagoni]

🎉 This PR is included in version 0.74.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀