chore(deps-dev): bump swagger-typescript-api from 9.3.1 to 12.0.3

[dependabot[bot]]

Bumps swagger-typescript-api from 9.3.1 to 12.0.3.

Release notes

Sourced from swagger-typescript-api's releases.

12.0.3 Release

What's Changed

• security: update the eta package to address CVE-2022-25967

Full Changelog: https://github.com/acacode/swagger-typescript-api/compare/12.0.2...12.0.3

12.0.2 Release

fix: missing option --extract-enums (#344)

12.0.1 Release

fix: problem based with http requests and disableStrictSSL option (#453)
docs: update docs for requestOptions nodejs option

12.0.0 Release

new hooks:

/** calls before parse\process route path */
onPreBuildRoutePath: (routePath: string) => string | void;
/** calls after parse\process route path */
onBuildRoutePath: (data: BuildRoutePath) => BuildRoutePath | void;
/** calls before insert path param name into string path interpolation */
onInsertPathParam: (paramName: string, index: number, arr: BuildRouteParam[], resultRoute: string) => string | void;
/** calls before parse any kind of schema */
onPreParseSchema: (originalSchema: any, typeName: string, schemaType: string) => any;

BREAKING_CHANGE: add ability to custom prefix for autofix invalid enum keys, invalid type names with nodejs options (fixInvalidTypeNamePrefix: string, fixInvalidEnumKeyPrefix: string)
BREAKING_CHANGE: by default all component enum schemas (even numeric) extracting as enum TS constructions (#344)
feature: ability to extract all enums from nested types\interfaces to enum TS construction using --extract-enums option (#344)
feature: ability to modify route path params before insert them into string (request url, #446, with using hook onInsertPathParam)
feature: (nodejs) ability to add prefix\suffix for type names and enum keys

typePrefix?: string;
typeSuffix?: string;
enumKeyPrefix?: string;
enumKeySuffix?: string;

feature: ability to customize resolving process of the extracting type names (extractingOptions nodejs option)

extractingOptions = {
  // requestBodySuffix: ["Payload", "Body", "Input"],
  // or
  // requestBodyNameResolver: (typeName, reservedNames) => string;
// requestParamsSuffix: ["Params"],
// or
// requestParamsNameResolver: (typeName, reservedNames) => string;
// responseBodySuffix: ["Data", "Result", "Output"],
</tr></table>

... (truncated)

Changelog

Sourced from swagger-typescript-api's changelog.

12.0.3

security: update the eta package to address CVE-2022-25967

12.0.2

fix: missing option --extract-enums (#344)

12.0.1

fix: problem based with http requests and disableStrictSSL option (#453) docs: update docs for requestOptions nodejs option

12.0.0

new hooks:

/** calls before parse\process route path */
onPreBuildRoutePath: (routePath: string) => string | void;
/** calls after parse\process route path */
onBuildRoutePath: (data: BuildRoutePath) => BuildRoutePath | void;
/** calls before insert path param name into string path interpolation */
onInsertPathParam: (paramName: string, index: number, arr: BuildRouteParam[], resultRoute: string) => string | void;
/** calls before parse any kind of schema */
onPreParseSchema: (originalSchema: any, typeName: string, schemaType: string) => any;

BREAKING_CHANGE: add ability to custom prefix for autofix invalid enum keys, invalid type names with nodejs options (fixInvalidTypeNamePrefix: string, fixInvalidEnumKeyPrefix: string) BREAKING_CHANGE: by default all component enum schemas (even numeric) extracting as enum TS constructions (#344) feature: ability to extract all enums from nested types\interfaces to enum TS construction using --extract-enums option (#344) feature: ability to modify route path params before insert them into string (request url, #446, with using hook onInsertPathParam) feature: (nodejs) ability to add prefix\suffix for type names and enum keys

typePrefix?: string;
typeSuffix?: string;
enumKeyPrefix?: string;
enumKeySuffix?: string;

feature: ability to customize resolving process of the extracting type names (extractingOptions nodejs option)

extractingOptions = {
  // requestBodySuffix: ["Payload", "Body", "Input"],
  // or
  // requestBodyNameResolver: (typeName, reservedNames) => string;
// requestParamsSuffix: ["Params"],
// or
// requestParamsNameResolver: (typeName, reservedNames) => string;
// responseBodySuffix: ["Data", "Result", "Output"],
// or
</tr></table>

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Superseded by #323.