"parameters" is a required property even if all parameters are optional

[denisw]

Description

When an operation has only optional parameters are defined, the generated operation typings still output parameters as a required property, even though all properties within are optional. This means that when using the schema with openapi-fetch, I have to pass { parameters: {} } instead of just {} if I don't want to pass any of the optional parameters.

Name	Version
openapi-typescript	6.5.5
Node.js	18.17.0
OS + version	macOS 13.5.1

Reproduction

Generate typings for a path with only optional parameters, e.g.:

paths:
  /foo:
    operationId: foo
    parameters:
      - in: header
        name: optional-header
        required: false
    responses:
      200:
        description: Success

Expected result

I would expect parameters to be optional in the generated operation type, like this:

export interface operations {
  // ...
  foo: {
    parameters?: {
      header?: {
        "optional-header"?: string;
      };
    };
    // ...
  };
}

Instead, parameters is defined as a required property.

Checklist

• My OpenAPI schema passes the Redocly validator (npx @redocly/cli@latest lint)
• I’m willing to open a PR (see CONTRIBUTING.md)