An OpenAPI Generator Plus template for a TypeScript API client using Fetch in Node. For an API client to use in browsers, see typescript-fetch-client-generator.
See the OpenAPI Generator Plus documentation for how to use generator templates.
The available config file properties are:
Property | Type | Description | Default |
---|---|---|---|
relativeSourceOutputPath |
string |
The path to output generated source code, relative to the output path. |
./ or ./src if npm is specified. |
Property | Type | Description | Default |
---|---|---|---|
constantStyle |
`"allCapsSnake" | "allCaps" | "camelCase" |
enumMemberStyle |
"preserve" | "constant"
|
The style to use for enum member names: preserve attempts to match the enum member name to the literal enum value from the spec; constant uses the constantStyle rules. |
"constant" |
legacyUnnamespacedModelSupport |
boolean |
Generate unnamespaced versions of the models. | false |
dateApproach |
`"native" | "string" | "blind-date"` |
A tsconfig.json
file will be output if you specify any of the TypeScript config options.
Property | Type | Description | Default |
---|---|---|---|
typescript |
TypeScriptConfig |
Configuration for the tsconfig.json file. |
undefined |
Property | Type | Description | Default |
---|---|---|---|
target |
string |
The ECMAScript target version. | ES5 |
Property | Type | Description | Default |
---|---|---|---|
npm |
NpmConfig |
Configuration for generating an npm package.json
|
undefined |
Property | Type | Description | Default |
---|---|---|---|
name |
string |
The package name | typescript-fetch-api |
version |
string |
The package version | 0.0.1 |
repository |
string |
The URL to the package repository | undefined |
Property | Type | Description | Default |
---|---|---|---|
customTemplates |
string |
The path to a directory containing custom Handlebars templates, relative to the config file. See Customising below. | undefined |
This generator supports a customTemplates
config file property to specify a directory containing Handlebars templates that will be used to override built-in templates.
Any custom template will have the original template available as a partial named by prefixing the template name with original
, and then upper-casing the first letter, e.g. originalModelEnum
.
Some of the templates in the generator are designed to support overriding for custom requirements. Please inspect the templates in the templates
directory.