fix: forward path-parameter model name for OpenAPI http_client operations

[ALagoni97]

Problem

For OpenAPI inputs, the http_client channels generator pushed every operation into renderedFunctions with a hardcoded parameterType: undefined (src/codegen/generators/typescript/channels/openapi.ts). It forwarded messageType/replyType but dropped the path-parameter information entirely.

Downstream consumers rely on parameterType to know whether an operation requires a parameters argument. In particular, README generation (in the platform-and-services library) uses it to decide whether to show a parameters line in the usage example and to pick a genuinely argument-free "primary" example.

Because it was always undefined, the generated README could:

• advertise a call that omits the required parameters for path-parameter operations — e.g. getV2ConnectReferenceId for GET /v2/connect/{referenceId} — yielding a snippet that does not type-check (Property 'parameters' is missing in type … but required in type 'GetV2ConnectReferenceIdContext'); and
• select such an operation as the "simple" primary example, since every operation looked parameter-free.

The functions themselves were always exported correctly — this is purely about the metadata that drives documentation/examples.

Fix

• Add parameterType?: string to HttpRenderType and populate it in renderHttpFetchClient with the parameter model name (channelParameters?.name) when the operation declares path parameters.
• Forward r.parameterType (instead of undefined) through renderedFunctions in the OpenAPI channels generator.

Operations without path parameters continue to report undefined.

Verification

• npm run typecheck — clean.
• npm test -- --testPathPattern=channels.spec — 13 passed, snapshots unchanged.
• Added a regression assertion to the existing OpenAPI http_client test: a path-parameter operation (findPetsByStatusAndCategory) now exposes parameterType: 'FindPetsByStatusAndCategoryParameters', while a parameter-free operation reports undefined.
• End-to-end against a real OpenAPI spec: the generated README now selects an operation with no required path parameters as the primary example and labels required payload/parameters correctly, instead of silently dropping a required parameters argument.

🤖 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 8, 2026 5:12pm
the-codegen-project-mcp	Ready	Preview, Comment	Jul 8, 2026 5:12pm

[jonaslagoni]

🎉 This PR is included in version 0.72.9 🎉

The release is available on:

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

Your semantic-release bot 📦🚀