TypeSpec

Describe your data up front and generate schemas, API specifications, clien...

OpenAPISchema
microsoft/typespecmicrosoft.github.io/typespec/@typespec/compiler

README

TypeSpec


TypeSpec is a language for defining cloud service APIs and shapes. TypeSpec is a highly extensible language with primitives that can describe API shapes common among REST, OpenAPI, gRPC, and other protocols.

TypeSpec is excellent for generating many different API description formats, client and service code, documentation, and many other assets. All this while keeping your TypeSpec definition as a single source of truth.

Using TypeSpec, you can create reusable patterns for all aspects of an API and package those reusable patterns into libraries. These patterns establish "guardrails" for API designers and makes it easier to follow best practices than to deviate from them. TypeSpec also has a rich linter framework with the ability to flag anti-patterns as well as an emitter framework that lets you control of the output to ensure it follows the patterns you want.

Installation


  1. ```
  2. npm install -g @typespec/compiler
  3. ```

Tools


The TypeSpec VS Code extension can be installed from the VS Code marketplace or directly on the command line:

  1. ```
  2. tsp code install
  3. ```

The TypeSpec VS Extension can be installed from the VS Marketplace or directly on the command line:

  1. ```
  2. tsp vs install
  3. ```

Usage


TypeSpec to OpenAPI 3.0 Example


This example uses the @typespec/http, @typespec/rest, and @typespec/openapi3 libraries to define a basic REST service and generate an OpenAPI 3.0 document from it.

Run the following command and select "Generic REST API":

  1. ```
  2. tsp init
  3. ```

Hit enter a few times to confirm the defaults.

Copy the contents below into your main.tsp:

  1. ```typespec
  2. import "@typespec/http";
  3. import "@typespec/rest";
  4. import "@typespec/openapi3";

  6. using TypeSpec.Http;
  7. using TypeSpec.Rest;

  9. /** This is a pet store service. */
  10. @service({
  11.   title: "Pet Store Service",
  12. })
  13. @server("https://example.com", "The service endpoint")
  14. namespace PetStore;

  16. @route("/pets")
  17. interface Pets {
  18.   list(): Pet[];
  19. }

  21. model Pet {
  22.   @minLength(100)
  23.   name: string;

  25.   @minValue(0)
  26.   @maxValue(100)
  27.   age: int32;

  29.   kind: "dog" | "cat" | "fish";
  30. }
  31. ```

Install the dependencies of main.tsp:

  1. ```
  2. tsp install
  3. ```

Compile it to OpenAPI 3.0:

  1. ```
  2. tsp compile main.tsp --emit @typespec/openapi3
  3. ```

You can find the emitted OpenAPI output in ./tsp-output/openapi.json.

Advanced Scenarios


Installing nightly version


On every commit to the main branch, packages with changes are automatically published to npm with the @next tag.
The packages section shows which version corresponds to thenext tag for each package.

To use a nightly version of the packages, go over each one of the packages in the package.json file and update it to either the latest published @next version or @latest, whichever is the newest. You can also use the tag latest or next instead of an explicit version.

After updating the package.json file you can run npm update --force. Force is required as there might be some incompatible version requirement.

Example

  1. ```json5
  2. // Stable setup
  3. "dependencies": {
  4.   "@typespec/compiler": "~0.30.0",
  5.   "@typespec/http": "~0.14.0",
  6.   "@typespec/rest": "~0.14.0",
  7.   "@typespec/openapi": "~0.9.0",
  8. }

  10. // Consume next version
  11. // In this example: compiler and openapi have changes but rest library has none
  12. "dependencies": {
  13.   "@typespec/compiler": "~0.31.0-dev.5",
  14.   "@typespec/http": "~0.14.0",
  15.   "@typespec/rest": "~0.14.0", // No changes to @typespec/rest library so need to stay the latest.
  16.   "@typespec/openapi": "~0.10.0-dev.2",
  17. }
  18. ```