swagger-typed-express-docs-test v0.0.2
swagger-typed-express-docs
swagger-typed-express-docs keep you simple document your endpoints with just one single source of truth which
- Generate Swagger API documentation
- Compile time validations - Infer Typescript static types out of the box
- Runtime validate each of your HTTP request with user-friendly error messages
To do that there is just a simple high-order-function API.
So you can just simply wrap your endpoint with the apiDoc(...)
and initialize project via initApiDocs()
Example usage
You can see full app example in the repository:
import express from 'express'
import { apiDoc, initApiDocs, tNonNullable, tString } from 'swagger-typed-express-docs'
import swaggerUi from 'swagger-ui-express'
const app = express()
const port = 3000
app.get(
'/user/:userId',
/**
* adding metadata for handlers where we want to have
* - runtime checks
* - compile-time checks
* - generate swagger documentation
*/
apiDoc({
params: {
userId: tNonNullable(tString),
},
query: {
name: tNonNullable(tString),
header: tList(tNonNullable(tUnion(['a', 'b', 'c'] as const))),
},
body: {
header: tList(tNonNullable(tUnion(['a', 'b', 'c'] as const))),
message: tNonNullable(tString),
footer: tString,
},
returns: tObject({
enhancedBody: tObject({
data: tUnion(['a', 'b', 'c'] as const),
}),
}),
})((req, res) => {
const body = req.body
const query = req.query
res.send({
body,
query,
})
})
)
/**
* before you start the server you have to setup library
*/
const swaggerJSON = initApiDocs(app, { info: { title: 'my application' } })
app.use('/api-docs', swaggerUi.serve, swaggerUi.setup(swaggerJSON))
Package API
The whole library expose 2 main functions: initApiDocs(...)
and & apiDoc(...)
initApiDocs
This method takes a swagger metadata which will be deeply merged into generated documentation.
initApiDocs()
returns generated Swagger JSON which you can use to document your API.
const swaggerJSON = initApiDocs(app, { info: { title: 'my application' } })
to make the application work you have to call initApiDocs()
at the end of routes definition
and before you start app.listen(...)
apiDoc
apiDoc(...)
is high-order-function which you use to wrap express endpoint handler
and define a meta-information about inputs & outputs of each API handler.
example usage:
app.get(
'/',
apiDoc({
query: {
name: tNonNullable(tString),
header: tList(tNonNullable(tUnion(['a', 'b', 'c'] as const))),
},
body: {
header: tList(tNonNullable(tUnion(['a', 'b', 'c'] as const))),
message: tNonNullable(tString),
footer: tString,
},
returns: tObject({
data: tObject({
nestedData: tUnion(['a', 'b', 'c'] as const),
}),
}),
})((req, res) => {
const body = req.body
const query = req.query
res.send({
body,
query,
})
})
)
The library exposes many functions and objects which help you to create schema as you want.
- tBoolean
- tNumber
- tUnion
- tNonNullable
- tAny
- tObject
- tCustomScalar
- tString
if you want to see more examples on how to build schema structure by function compositions you can check the tests
Setup environments
Express body parsing
if you want to parser body, you have to setup body parser express middleware.
app.use(express.json())
Express query parsing
You can parse query thanks to express-query-parser
library.
import { queryParser } from 'express-query-parser'
app.use(
queryParser({
parseNull: true,
parseBoolean: true,
})
)
Typescripts null checks
to make fully work tNonNullable
you have to setup tsconfig.json
properly.
{
...
"compilerOptions": {
...
"strictNullChecks": true,
}
}
Example library preview
Decorators vs High order function
Author of the library decide to use simple pure Javascript High-order-function instead of fancy pants class based decorators API to simple keep good old express API of endpoints and not to be dependent on compilers options. If you want to know more about it, check this article
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago