I’m proud to announce that I’m now a member of the Swagger Codegen Core team.
I’ve previously refactored the C# client, the maven plugin, added an ASP.NET 5 Web API server generator, and fixed some bugs.
. ├── IO.Swagger.sln ├── README.md ├── bin ├── build.bat ├── build.sh ├── docs ├── packages └── src ├── IO.Swagger │ └── packages.config └── IO.Swagger.Test └── packages.config
With this breaking change and the .swagger-codegen-ignore, users can now generate into existing repositories. Suppose your project is setup this way:
. ├── MyProject.sln ├── README.md ├── bin ├── build.bat ├── build.sh ├── docs ├── packages └── src ├── MyProject │ └── packages.config └── MyProject.Test └── packages.config
You may want your generated client code to be output under src/MyProject.Client, but you don’t want build.bat, build.sh, or docs to get blown away. Last week, I partially resolved this by adding options to disable api and model doc generation for all languages… but there was no clean way to ignore other files like build.bat or build.sh.
Now, you can add the following .swagger-codegen-ignore to your existing directory structure:
# Swagger Codegen Ignore /README.md /build.* docs/ src/ !src/MyProject.Client/ !src/MyProject.Client.Test/
Just to be safe (this feature is brand new), commit and push your changes before running swagger-codegen using your repository as the output directory. You should end up with the following structure:
. ├── .swagger-codegen-ignore ├── IO.Swagger.sln ├── MyProject.sln ├── README.md ├── bin ├── build.bat ├── build.sh ├── docs ├── packages └── src ├── MyProject │ └── packages.config ├── MyProject.Test │ └── packages.config ├── IO.Swagger │ └── packages.config └── IO.Swagger.Test └── packages.config
As expected, the only generated content should be the IO.Swagger.sln, src/IO.Swagger and src/IO.Swagger.Test.
All of the functionality in this post should land in version 2.2.0. Until then, you can build directly against the master branch for these features.