Installation

npm install -g autorest

Compatibility

This AutoRest extension generates TypeScript code that is compatible with:

"@azure/ms-rest-azure-js": "^1.2.0",
"@azure/ms-rest-js": "^1.2.0"

Usage

Basic Usage:

autorest --typescript \
  --input-file=<path-to-swagger-spec> \
  --output-folder=<path-to-the-output-folder(usually upto lib folder of your project)> \
  --license-header=MICROSOFT_MIT_NO_VERSION \
  --package-name=<your-package-name> \
  --package-version=<your-package-version>

If you have a markdown config file then there is no need to use --input-file, simply provide the path to the markdown file:

autorest --typescript \
  <path-to-readme.md> \
  --output-folder=<path-to-the-output-folder(usually upto lib or src folder of your project)> \
  --license-header=MICROSOFT_MIT_NO_VERSION \
  --package-name=<your-package-name> \
  --package-version=<your-package-version>

Flags

--generate-metadata

Generating metadata files enable you to build and pack the result as an NPM package. If you want to generate metadata files provide --generate-metadata=true

• package.json
• .npmignore
• webpack.config.js
• tsconfig.json
• README.md (with a sample)

NOTE:

• This will generate all the metadata files one level above the output-folder.
• The output-folder must end in the lib folder for now. For example --output-folder=D:\tmp\TSProject\lib. This is required because the includes array in tsconfig.json and stuff inside webpack.config.js is hardwired to look for the generated stuff inside the lib folder.

autorest --typescript \
  --output-folder=<path-to-the-output-folder(usually upto lib folder of your project)> \
  --license-header=MICROSOFT_MIT_NO_VERSION \
  --input-file=<path-to-swagger-spec> \
  --package-name=<your-package-name> \
  --package-version=<your-package-version> \
  --generate-metadata=true

--model-date-time-as-string

Swagger strings can have the format "date-time", which causes AutoRest to model the parameter as JavaScript Date.

  putDate(date: Date): Promise<RestResponse>;

If you pass --model-date-time-as-string=true to the generator, it will instead model and treat the ISO 8601 formatted date-time as a plain old string in the interfaces and at runtime. This allows users to use custom date formatting methods, particularly for services which are finicky about the accepted format of dates or require greater precision than what the JavaScript Date provides out of the box.

  putDate(date: string): Promise<RestResponse>;

--optional-response-headers

Swagger response headers don't have the ability to specify whether the header is required or optional. The generator will make the generated response headers all required by default.

export interface MyOperationHeaders {
  fooHeader: string;
  barHeader: string;
}

If you pass --optional-response-headers=true to the generator, it will instead make all the response headers optional.

export interface MyOperationHeaders {
  fooHeader?: string;
  barHeader?: string;
}

--source-code-folder-path

The folder relative to the output-folder path that the TypeScript source code files will be generated in. If no value is provided for this flag, then it will default to lib. If an empty string is provided for this flag, then the TypeScript source code files will be generated in the output-folder.

--azure-arm

For generating a client for an Azure service, provide --typescript.azure-arm=true:

autorest --typescript \
  --output-folder=<path-to-the-output-folder(usually upto lib folder of your project)> \
  --license-header=MICROSOFT_MIT_NO_VERSION \
  --input-file=<path-to-swagger-spec> \
  --package-name=<your-package-name> \
  --generate-metadata=true \
  --typescript.azure-arm=true

--add-credentials

If you want to use services which need authorization you need to generate a constructor taking msRest.ServiceClientCredentials. In order to to do so add --add-credentials as commandline parameter

autorest --typescript \
  --output-folder=<path-to-the-output-folder(usually upto lib folder of your project)> \
  --license-header=MICROSOFT_MIT_NO_VERSION \
  --input-file=<path-to-swagger-spec> \
  --package-name=<your-package-name> \
  --add-credentials=true

the generated constructor will look like

constructor(credentials: msRest.ServiceClientCredentials, options?: msRest.ServiceClientOptions)

--enum-types

By default, a Swagger enum is translated into a TypeScript enum, like so:

type Colors = 'red color' | 'green-color' | 'blue_color';

You may instead generate an actual enum type by passing --enum-types=true to AutoRest, which will instead produce:

enum Colors {
  RedColor = 'red color',
  GreenColor = 'green-color',
  BlueColor = 'blue_color',
}

Using string unions instead of enum types can produce more future-proof code, which is why we default to string unions.

--skip-subtypes

This parameter can be used to reduce the size of your generated mapper set for your MethodGroups. The mapper set is used during serialization and deserialization, so skipping subtypes may result in some types not being serialized or deserialized properly. For example, the following argument will include any types that are directly referenced by the MethodGroup's methods that "inherit" from BaseResource, Resource, or SubResource. It will not discover any additional types that inherit from BaseResource, Resource, or SubResource that are not specifically mentioned in the MethodGroup's methods.

autorest --typescript \
  --output-folder=<path-to-the-output-folder(usually upto lib folder of your project)> \
  --license-header=MICROSOFT_MIT_NO_VERSION \
  --input-file=<path-to-swagger-spec> \
  --package-name=<your-package-name> \
  --skip-subtypes=[BaseResource,Resource,SubResource]

Further Documentation on the Command Line

The complete list of command line arguments can be found here. Not every command line option is available for the typescript extension.

Deprecated Flags

--model-enum-as-union (deprecated)

This flag is now on by default and cannot be turned off. Swagger enum values are now always treated as a union of literal values.

Previous behavior (when --model-enum-as-union was false or not defined):

enum Colors {
  Redcolor = 'red color',
  GreenColor = 'green-color',
  BlueColor = 'blue_color',
}

Current behavior:

type Colors = 'red color' | 'green-color' | 'blue_color';

Development

Building the project

After cloning the repo, execute:

• npm install
• npm install -g gulp (gulp should be installed globally too)
• npm run build

IMPORTANT NOTE

This project uses a git submodule for dependent code. When cloning this repository use git clone --recursive ... or perform a git submodule update --init --recursive after the project is cloned.

Testing the developed changes

• gulp regenerate
• gulp test

Debugging using vscode

Add the --typescript.debugger to the command line and then use the Attach to Debugger option from vscode. Attach to the dotnet.exe process id that is provided in the command line. We have the .vscode folder in the repo that has the config for attaching to the debugger.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

AutoRest extension configuration

use-extension:
  "@microsoft.azure/autorest.modeler": "2.3.51"

pipeline:
  typescript/imodeler1:
    input: openapi-document/identity
    output-artifact: code-model-v1
    scope: typescript
  typescript/commonmarker:
    input: imodeler1
    output-artifact: code-model-v1
  typescript/cm/transform:
    input: commonmarker
    output-artifact: code-model-v1
  typescript/cm/emitter:
    input: transform
    scope: scope-cm/emitter
  typescript/generate:
    plugin: typescript
    input: cm/transform
    output-artifact: source-file-typescript
  typescript/transform:
    input: generate
    output-artifact: source-file-typescript
    scope: scope-transform-string
  typescript/emitter:
    input: transform
    scope: scope-typescript/emitter

scope-typescript/emitter:
  input-artifact: source-file-typescript
  output-uri-expr: $key

output-artifact:
- source-file-typescript