Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
routing-controllers
Create structured, declarative and beautifully organized class-based controllers with heavy decorators usage in Express / Koa using TypeScript and Routing Controllers Framework.
-
apifire
Generates node.js express validators / routers / controllers in Typescript using an OpenAPI 3.0 spec
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
foal
Full-featured Node.js framework, with no complexity. 🚀 Simple and easy to use, TypeScript-based and well-documented.
If so, how do you go about generating the interface files? I recently discovered swaggo which generates OpenAPI docs from Go annotations. My Googlefoo then led me to swagger-jsdoc and openapi-comment-parser which do the same thing from JSdoc-like comments. Do you use them, do you use some other module, or do you use some other approach entirely?
If so, how do you go about generating the interface files? I recently discovered swaggo which generates OpenAPI docs from Go annotations. My Googlefoo then led me to swagger-jsdoc and openapi-comment-parser which do the same thing from JSdoc-like comments. Do you use them, do you use some other module, or do you use some other approach entirely?
If so, how do you go about generating the interface files? I recently discovered swaggo which generates OpenAPI docs from Go annotations. My Googlefoo then led me to swagger-jsdoc and openapi-comment-parser which do the same thing from JSdoc-like comments. Do you use them, do you use some other module, or do you use some other approach entirely?
I currently use https://github.com/typestack/routing-controllers and https://github.com/epiphone/routing-controllers-openapi with https://github.com/Redocly/redoc
I currently use https://github.com/typestack/routing-controllers and https://github.com/epiphone/routing-controllers-openapi with https://github.com/Redocly/redoc
I currently use https://github.com/typestack/routing-controllers and https://github.com/epiphone/routing-controllers-openapi with https://github.com/Redocly/redoc
For https://emailengine.app I generate swagger docs with the hapi-swagger plugin https://github.com/hapi-swagger/hapi-swagger - the process is pretty much fully automatic as it uses the input and output schema validations.
For https://emailengine.app I generate swagger docs with the hapi-swagger plugin https://github.com/hapi-swagger/hapi-swagger - the process is pretty much fully automatic as it uses the input and output schema validations.
see: https://github.com/eclipse/microprofile-open-api/blob/master/spec/src/main/asciidoc/microprofile-openapi-spec.asciidoc
FoalTS allows you to generate your OpenAPI documentation directly from your code: https://foalts.org/docs/api-section/openapi-and-swagger-ui.
Thank you! I'm using Stoplight and am very happy with it. I ended up using openapi-typescript to generate interfaces from the .yaml published from Stoplight, I might use openapi-typescript-codegen for client SDK later on.