Parameters names are different from their usage names

What are the steps to reproduce this issue?

This might be related to using requestBodies as an abstraction layer between paths and schemas.

Fastest way to repro this is generate a client from this schema: https://github.com/Southclaws/storyden/blob/main/api/openapi.yaml

What happens?

Paths that have POST payloads specified as requestBody which $ref’s components/requestBodies will generate slightly different names for the parameters of the function compared to the actual invocations within the function:

In text form:

/**
 * @summary Register a new account with a username and password.
 */
export const authPasswordSignup = (authPasswordBody: AuthPasswordBody) => {
  const formUrlEncoded = new URLSearchParams();
  formUrlEncoded.append("identifier", authRequest.identifier);
  formUrlEncoded.append("token", authRequest.token);

  return customInstance<AuthSuccessResponse>({
    url: `/v1/auth/password/signup`,
    method: "post",
    headers: { "Content-Type": "application/x-www-form-urlencoded" },
    data: formUrlEncoded,
  });
};

In this code, the generated function parameter is called authPasswordBody but the invocations for calls to formUrlEncoded.append has generated authRequest.

Some observations here:

• The requestBody ref is named AuthPassword
• The actual schema referenced by the requestBody is named AuthRequest

What versions are you using?

Operating System: mac Package Version: v6.9.6

[anymaniax]

will be fixed in the next release

[Southclaws]

Working perfectly, thanks!