TypeSpec library for emitting OpenAPI 3.0 from the TypeSpec REST protocol binding

npm install @typespec/openapi3

1. Via the command line

tsp compile . --emit=@typespec/openapi3

2. Via the config

emit:
  - "@typespec/openapi3"

Type: "yaml" | "json"

If the content should be serialized as YAML or JSON. Default 'yaml', it not specified infer from the output-file extension

Type: string

Name of the output file. Output file will interpolate the following values:

• service-name: Name of the service if multiple
• version: Version of the service if multiple

Default: {service-name}.{version}.openapi.yaml or .json if file-type is "json"

Example Single service no versioning

• openapi.yaml

Example Multiple services no versioning

• openapi.Org1.Service1.yaml
• openapi.Org1.Service2.yaml

Example Single service with versioning

• openapi.v1.yaml
• openapi.v2.yaml

Example Multiple service with versioning

• openapi.Org1.Service1.v1.yaml
• openapi.Org1.Service1.v2.yaml
• openapi.Org1.Service2.v1.0.yaml
• openapi.Org1.Service2.v1.1.yaml

Type: "crlf" | "lf"

Set the newline character for emitting files.

Type: boolean

Omit unreachable types. By default all types declared under the service namespace will be included. With this flag on only types references in an operation will be emitted.

Type: "inline-only" | "never"

If the generated openapi types should have the x-typespec-name extension set with the name of the TypeSpec type that created it. This extension is meant for debugging and should not be depended on.

Type: "double-int" | "int64"

How to handle safeint type. Options are:

• double-int: Will produce type: integer, format: double-int
• int64: Will produce type: integer, format: int64

Default: int64

• @oneOf
• @useRef

Specify that oneOf should be used instead of anyOf for that union.

@TypeSpec.OpenAPI.oneOf

Union | ModelProperty

None

Specify an external reference that should be used inside of emitting this type.

@TypeSpec.OpenAPI.useRef(ref: valueof string)

Model | ModelProperty