fix(openapi3): avoid duplicating parameter @extension on schema

[timotheeguerin]

Fixes #8271

Problem

An @extension applied to a query/path/header parameter property was emitted twice: once on the OpenAPI Parameter Object root (correct) and once inside the nested schema object (unwanted duplicate).

{ "name": "filter", "in": "query", "required": true,
  "schema": { "type": "string", "x-my-ext": "hello" },
  "x-my-ext": "hello" }

Fix

In getOpenAPIParameterBase, the parameter property's own extension keys are stripped from the parameter schema (they remain on the Parameter Object root, consistent with the existing parameter component test and OpenAPI conventions).

Tests

Added a test asserting the extension is present on the parameter object and absent from its schema for both query and path parameters.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/openapi3@11204

commit: 86e9d68

[github-actions]

All changed packages have been documented.

• ✅ @typespec/openapi3

Show changes

@typespec/openapi3 - fix ✏️

Fix @extension being duplicated on both the parameter object and its schema in OpenAPI output. Parameter extensions are now emitted only on the parameter object.

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension