@tsed/swagger
A package of Ts.ED framework. See website: https://romakita.github.io/ts-express-decorators/#/tutorials/swagger
Installation
Before using the Swagger, we need to install the swagger-ui-express module.
npm install --save-dev @types/swagger-schema-official
npm install --save swagger-ui-express @tsed/swagger
Then add the following configuration in your ServerLoader:
import {ServerLoader, ServerSettings} from "@tsed/common";
import "@tsed/swagger";
import Path = require("path");
const rootDir = Path.resolve(__dirname)
@ServerSettings({
rootDir,
swagger: {
path: "/api-docs"
}
})
export class Server extends ServerLoader {
}
The path option for swagger will be used to expose the documentation (ex: http://localhost:8000/api-docs).
Normally, Swagger-ui is ready. You can start your server and check if it work fine.
Note: Ts.ED will print the swagger url in the console.
Swagger options
Some options is available to configure Swagger-ui, Ts.ED and the default spec information.
Key | Example | Description |
---|
path | /api-doc | The url subpath to access to the documentation. |
cssPath | ${rootDir}/spec/style.css | The path to the CSS file. |
showExplorer | true | Display the search field in the navbar. |
spec | {swagger: "2.0"} | The default information spec. |
specPath | ${rootDir}/spec/swagger.json | The path to the swagger.json. This file will be written at the first server starting if it doesn't exist. The data will me merge with the collected data via annotation. |
Examples
Model documentation
One of the feature of Ts.ED is the model definition to serialize or deserialize a
JSON Object (see converters section).
This model can used on a method controller along with @BodyParams or other decorators.
import {JsonProperty} from "@tsed/common";
import {Title, Description, Example} from "@tsed/swagger";
export class CalendarModel {
@Title("iD")
@Description("Description of calendar model id")
@Example("example1", "Description example")
@JsonProperty()
public id: string;
@JsonProperty()
public name: string;
}
Endpoint documentation
import {Controller, Get, Post} from "@tsed/common";
import {Summary, Description, Responses,Deprecated, Security} from "@tsed/swagger";
@Controller('/calendars')
export class Calendar {
@Get('/:id')
@Summary("Summary of this route")
@Description("Description of this route")
@Returns("404", {description: "Not found"})
async getCalendar(@QueryParam() id: string): Promise<CalendarModel> {
}
@Get('/v0/:id')
@Deprecated()
@Description("Deprecated route, use /rest/calendars/:id instead of.")
@Returns("404", {description: "Not found"})
getCalendarDeprecated(@QueryParam() id: string): Promise<CalendarModel> {
}
@Post('/')
@Security("calendar_auth", "write:calendar", "read:calendar")
async createCalendar(): Promise<CalendarModel> {
}
}
!> To update the swagger.json you need to reload the server before.
Documentation
See our documentation https://romakita.github.io/ts-express-decorators/#/api/index
Contributors
Please read contributing guidelines here.
Backers
Thank you to all our backers! 🙏 [Become a backer]
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
License
The MIT License (MIT)
Copyright (c) 2016 - 2018 Romain Lenzotti
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.