Nathan Klisch

I wrote up a dependency free Typescript npm package that parses complex express apps and outputs a list of data per route and allows attaching meta-data to each route, if...

@brunolnetto I'll take a look

@brunolnetto For swagger ui try: router.use('/swagger"', swaggerUi.serve); router.get('/swagger", swaggerUi.setup(swaggerDocument)); instead of just one app.use() line. But for swagger-stats, I looked into how they do their routing, and unfortunately they have...

I would like this feature - or perhaps someway to feed in our own node/js formatter as middleware - such as pino-pretty: https://github.com/pinojs/pino-pretty#options would be awesome - not sure the...

With volume mapping, you could make a docker container where people would map their logs into the docker container for the log viewer to see. Similar to the suggestion above...

There is no need for additional development @sevdokimov, I created a Dockerfile and a docker compose file that packages the software and lets them pass in their own config file,...

I have experienced this issue as well. I might look at trying to do a PR for it, cause I don't like repeating simple path parameters like {id} for a...

This seems to still be an open issue, as I am seeing this problem as well

@anttiviljami The second PR on this issue seems rather stale, would you accept a new one to parse, and if the user choses, coerce the types via AJV coerceTypes option?

Also, I'd like to update the Context object type so it can take in a type for the params, allowing typescript intellisense, like how Express requests work, since we are...