Motivation

In some usecases, we expect to do deepcopy for api types. It would be more efficient to generate deepcopy code for swagger model.

Proposal

Generate DeepCopy() $object method for each swagger model. We can take reference to https://github.com/kubernetes/code-generator.

Hi together,

I just started using swagger-jsdoc in my nodejs project using Typescript. It was kind of hard to figure out how to use it due to the transpilation process involved.

There are a few workarounds necessary to make it work:

• apis [...] has to point to files in the /dist directory due to the transpilation process
• Annotations (in the comments) to model classes are lost in the t

Thanks for the great project! I just wanted to suggest adding some details to the documentation regarding usage as well as dependencies.

It's true that all of these things are available in the code via tests but it's not super intuitive where to find them. As I write this I know that I found the usage; it's fairly easy but since I didn't commit it to memory I'll have to dig through the tests ag

We need to add finnish translation to about.html (the info texts you see when enter the main site).

Replace it with a link to the official documentation that will be the "official" version of the roadmap.

Steps:

1. Create a roadmap page in the official documentation
2. Publish
3. Add a link to this in the readme.

Besides just checking if a preprocessor variable has a given value (@rest\if name value) it would be very helpful to have its value inserted somewhere inside the documentation.
For example instead of incrementing the API version manually as in
// @rest\version 0.9.14

I would like to have it changed automatically like:
// @rest\version {myversion}
`$SwaggerGen->define('myversio

If the service no longer support a mime-type/data format, e.g. "application/json" or xml, it would be a breaking change for the users. There should be rules detecting these changes.