feat(openapi): add x-fern-parameter-name support for websocket query parameters #11376
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Refs: Slack thread from @aditya-arolkar-swe
Link to Devin run: https://app.devin.ai/sessions/2143d4e4bc654af4b7ca3d0aee402c1c
This PR adds support for the
x-fern-parameter-nameextension on websocket query parameters in AsyncAPI specs. Previously, this extension was only supported for HTTP endpoint parameters, and websocket query parameters always hadparameterNameOverrideset toundefined.This enables users to rename websocket query parameters in generated SDKs to avoid naming conflicts (e.g., when a query parameter and an event type would generate the same property name).
Changes Made
parseAsyncAPIV2.tsto extractx-fern-parameter-nameextension for websocket query parameters (both reference and non-reference schemas)parseAsyncAPIV3.tsto extractx-fern-parameter-nameextension for websocket channel parametersasyncapi-websocket-parameter-nameto validate the featureTesting
Human Review Checklist
convertParameters.tsname:field for overridden parameters (visible in snapshot atchat.yml)