"securityWorker" is only used if "secure" option is specified on each request

[dkamyshov]

Hi! Thanks for the great package.

This seems to be a Fetch API variation of another issue - #192.

Here is what the request method looks like after generating the API with the following parameters:

$ yarn swagger-typescript-api -p ./source.json -o . -n result.ts

class Api {
  // ...

  public request = async <T = any, E = any>({
    body,
    secure,
    // ...
    ...params
  }: FullRequestParams): Promise<HttpResponse<T, E>> => {
    // the "secure" option from this.baseApiParams is not used here
    const secureParams =
      (secure &&
        this.securityWorker &&
        (await this.securityWorker(this.securityData))) ||
      {};

    const requestParams = this.mergeRequestParams(params, secureParams);

    // ...
  };
}

So, basically, when the Fetch API is used, there is no way to make use of securityWorker other than specifying secure on each request. With axios this is solved trivially with interceptors, but I'd like to continue using the Fetch API.

Here is a simple reproduction of the issue (v7.0.0, just run $ yarn): https://github.com/dkamyshov/swagger-typescript-api-bug-repro

swagger-typescript-api	6.4.2, 7.0.0

[dkamyshov]

Replacing secure with (typeof secure === 'boolean' ? secure : this.baseApiParams.secure) (no ?? for Node 12, ofc) here and here is probably enough. I can open a PR if you approve this.

[js2me]

@dkamyshov please open a PR, I'll approve this.
Please use the next branch

[js2me]

@dkamyshov thank you for your contribution!
This problem should be fixed in 7.0.1

[dkamyshov]

@js2me thanks for quick response, it works flawlessly now.