Package Exports
- ts-openapi
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ts-openapi) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Ts-openapi
An openapi json generator using joi API schemas that will help you to maintain your API documentation up to date. Joi is the is one of the most used components to validate data schemas, this can be used to generate and maintain API information up to date, without the need to update manually documentation.
This software has some code extracted from joi-to-swagger to interface with Joi schemas.
Installation
Using npm:
npm i --save ts-openapi
Visit the GitHub Repo tutorials, documentation, and support
OpenApi Supported Types
Type | Query | Path (1)(6) | Header | Cookie | Body |
---|---|---|---|---|---|
String, String Enum, Email, Password, Uuid, Uri, Hostname, Ipv4, Ipv6 | YES | YES | YES | YES | NO (5) |
Integer, Integer Enum, Number, Number Enum | YES | YES | YES | YES | NO (5) |
Date-time, Date | YES | YES | YES | YES | NO (5) |
Byte(3), Binary (string) | YES | YES | YES | YES | NO (5) |
Array[] | YES (4) | NO | NO | NO | NO (2)(5) |
Object | NO | NO | NO | NO | YES (7) |
(1) Values included in url parameters are always required because they're part of the url. |
|||||
(2) Ajax bestpractices. |
|||||
(3) this type is a Base64 binary encoded string. |
|||||
(4) array of scalar values. |
|||||
(5) all scalar values, arrays of objects and other objects go inside json object. |
|||||
(6) the name of route parameters must be made up of “word characters” ([A-Za-z0-9_]). |
|||||
(7) GET requests don't have a body. |
|||||
Type Samples
All samples presented here an in Typescript
String Types
Numeric Types
Date-Time Types
Binary Types
Array Type
Object Type
Security Schemes
Declaring an API
First we need to create an OpenApi object to store information
const openApi = new OpenApi(
"1.0.0", // API version
"Server API", // API title
"Some test api", // API description
"maintainer@domain.com" // API maintainer email
);
Then you need to declare an array with the API servers
In the event your API is based on docker instances you should call setServers when OpenApi class is called to get the json, to update the IPs and port numbers. You can even specify different servers depending if the call is internal or external. Up to you.
openApi.setServers([
{ url: "https://api.domain.com:443" },
{ url: "https://192.168.1.23:80" }
]);
Now you need to declare your endpoints (once per http verb)
openApi.addPath(
"/hello",
{
get: {
summary: "Server Healthcheck", // Method title
description: "Hello world endpoint", // Method description
operationId: "hello-op", // unique operation id
responses: { // response codes and description
200: textPlain("Successful operation."),
/* // or if you prefer:
200: {
description: "Successful operation.",
content: { "text-plain": {} }, // mimetype with empty schema
},*/
},
tags: ["Test Operations"], // One or more tags, this will allow API grouping
},
},
true // visible ? If not it gets skipped from declaration
);
Finally we export the JSON schema
Note that the paths just need to be added one time, during server init, after this the openApi is basically static.
openApi.generateJson();
Declaring a GET request
function errorSchema(description: string) {
return bodySchema(
Types.Object({
description,
properties: {
message: Types.String({ description: "Error message" }),
code: Types.Integer({ description: "Error code" }),
},
})
);
}
// body response schema
const responseSchema = {
id: Types.Uuid({ description: "Customer ID" }),
name: Types.String({
description: "Customer name",
maxLength: 100,
required: true,
}),
type: Types.StringEnum({
values: Object.values(CustomerType),
description: "Customer Type",
}),
birthdate: Types.Date({ description: "Birthdate" }),
};
openApi.addPath(
"/customer/:id", // path parameter
{
get: {
summary: "Get a customer data",
description: "This operation retrieves customer information",
operationId: "get-customer-op",
requestSchema: {
params: { // path parameter
id: Types.Uuid({
description: "Customer ID",
required: true, // param values MUST be required
example: "37237d6a-bb7e-459a-b75d-d1733210ad5c",
}),
},
},
tags: ["Customer Operations"],
responses: {
200: bodySchema(
Types.Object({
description: "Successful Operation",
properties: responseSchema,
})
),
400: errorSchema("Bad Request"),
},
},
},
true
);
Declaring other HTTP methods
You can declare:
- get requests
- post requests
- delete requests
- put methods
Declaring the inputs of your request
When you declare your request you can use as inputs:
- query parameters '?a=1&b=2'
- param parameter '/:userid/list'
- cookie parameter (a cookie)
- header parameters
- body content