Name: swagger-codegen
Owner: Hortonworks Inc
Description: swagger-codegen contains a template-driven engine to generate documentation, API clients and server stubs in different languages by parsing your OpenAPI / Swagger definition.
Forked from: swagger-api/swagger-codegen
Created: 2017-02-09 22:11:02.0
Updated: 2017-02-09 22:11:13.0
Pushed: 2017-02-09 22:13:25.0
Homepage: http://swagger.io
Size: 44944
Language: HTML
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
:star::star::star: If you would like to contribute, please refer to guidelines and a list of open tasks.:star::star::star:
:notebook_with_decorative_cover: For more information, please refer to the Wiki page and FAQ :notebook_with_decorative_cover:
:warning: If the OpenAPI/Swagger spec is obtained from an untrusted source, please make sure you've reviewed the spec before using Swagger Codegen to generate the API client, server stub or documentation as code injection may occur :warning:
This is the swagger codegen project, which allows generation of API client libraries (SDK generation), server stubs and documentation automatically given an OpenAPI Spec. Currently, the following languages/frameworks are supported:
Check out OpenAPI-Spec for additional information about the OpenAPI project.
The OpenAPI Specification has undergone 3 revisions since initial creation in 2010. The swagger-codegen project has the following compatibilities with the OpenAPI Specification:
Swagger Codegen Version | Release Date | OpenAPI Spec compatibility | Notes ————————– | ———— | ————————– | —– 2.3.0 (upcoming minor release) | TBD | 1.0, 1.1, 1.2, 2.0 | Minor release with breaking changes 2.2.2 (upcoming patch release) | TBD | 1.0, 1.1, 1.2, 2.0 | Patch release (without breaking changes) 2.2.1 (current stable) | 2016-08-07 | 1.0, 1.1, 1.2, 2.0 | tag v2.2.1 2.1.6 | 2016-04-06 | 1.0, 1.1, 1.2, 2.0 | tag v2.1.6 2.0.17 | 2014-08-22 | 1.1, 1.2 | tag v2.0.17 1.0.4 | 2012-04-12 | 1.0, 1.1 | tag v1.0.4
If you're looking for the latest stable version, you can grab it directly from maven central (you'll need java 7 runtime at a minimum):
http://repo1.maven.org/maven2/io/swagger/swagger-codegen-cli/2.2.1/swagger-codegen-cli-2.2.1.jar -O swagger-codegen-cli.jar
-jar swagger-codegen-cli.jar help
On a mac, it's even easier with brew:
install swagger-codegen
To build from source, you need the following installed and available in your $PATH:
Don't forget to install Java 7 or 8. You probably have 1.6.
Export JAVA_HOME in order to use the supported Java version:
rt JAVA_HOME=`/usr/libexec/java_home -v 1.8`
rt PATH=${JAVA_HOME}/bin:$PATH
After cloning the project, you can build it from source with this command:
clean package
To install, run brew install swagger-codegen
Here is an example usage:
ger-codegen generate -i http://petstore.swagger.io/v2/swagger.json -l ruby -o /tmp/test/
You can use run-in-docker.sh to do all development. This script maps your local repository to /gen
in the docker container. It also maps ~/.m2/repository to the appropriate container location.
To execute mvn package:
clone https://github.com/swagger-api/swagger-codegen
wagger-codegen
n-in-docker.sh mvn package
Build artifacts are now accessible in your working directory.
Once built, run-in-docker.sh will act as an executable for swagger-codegen-cli. To generate code, you'll need to output to a directory under /gen (e.g. /gen/out). For example:
n-in-docker.sh help # Executes 'help' command for swagger-codegen-cli
n-in-docker.sh langs # Executes 'langs' command for swagger-codegen-cli
n-in-docker.sh /gen/bin/go-petstore.sh # Builds the Go client
n-in-docker.sh generate -i modules/swagger-codegen/src/test/resources/2_0/petstore.yaml \
-l go -o /gen/out/go-petstore -DpackageName=petstore # generates go client, outputs locally to ./out/go-petstore
Prerequisite: install Vagrant and VirtualBox.
clone http://github.com/swagger-api/swagger-codegen.git
wagger-codegen
ant up
ant ssh
vagrant
n-in-docker.sh mvn package
The Swagger Generator image can act as a self-hosted web application and API for generating code. This container can be incorporated into a CI pipeline, and requires at least two HTTP requests and some docker orchestration to access generated code.
Example usage (note this assumes jq is installed for command line processing of JSON):
art container and save the container id
$(docker run -d swaggerapi/swagger-generator)
low for startup
p 5
t the IP of the running container
IP=$(docker inspect --format '{{.NetworkSettings.IPAddress}}' $CID)
ecute an HTTP request and store the download link
LT=$(curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{
waggerUrl": "http://petstore.swagger.io/v2/swagger.json"
http://localhost:8188/api/gen/clients/javascript' | jq '.link' | tr -d '"')
wnload the generated zip and redirect to a file
$RESULT > result.zip
utdown the swagger generator image
er stop $CID && docker rm $CID
In the example above, result.zip will contain the generated client.
The Swagger Codegen image acts as a standalone executable. It can be used as an alternative to installing via homebrew, or for developers who are unable to install Java or upgrade the installed version.
To generate code with this image, you'll need to mount a local location as a volume.
Example:
er run --rm -v ${PWD}:/local swagger-api/swagger-codegen generate \
-i http://petstore.swagger.io/v2/swagger.json \
-l go \
-o /local/out/go
The generated code will be located under ./out/go in the current directory.
To generate a PHP client for http://petstore.swagger.io/v2/swagger.json, please run the following
clone https://github.com/swagger-api/swagger-codegen
wagger-codegen
clean package
-jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar generate \
i http://petstore.swagger.io/v2/swagger.json \
l php \
o /var/tmp/php_api_client
(if you're on Windows, replace the last command with java -jar modules\swagger-codegen-cli\target\swagger-codegen-cli.jar generate -i http://petstore.swagger.io/v2/swagger.json -l php -o c:\temp\php_api_client)
You can also download the JAR (latest release) directly from maven.org
To get a list of general options available, please run java -jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar help generate
To get a list of PHP specified options (which can be passed to the generator with a config file via the -c option), please run java -jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar config-help -l php
You can build a client against the swagger sample petstore API as follows:
n/java-petstore.sh
(On Windows, run .\bin\windows\java-petstore.bat instead)
This will run the generator with this command:
-jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar generate \
http://petstore.swagger.io/v2/swagger.json \
java \
samples/client/petstore/java
with a number of options. You can get the options with the help generate command:
swagger-codegen-cli generate - Generate code with chosen lang
PSIS
swagger-codegen-cli generate
[(-a <authorization> | --auth <authorization>)]
[--additional-properties <additional properties>]
[--api-package <api package>] [--artifact-id <artifact id>]
[--artifact-version <artifact version>]
[(-c <configuration file> | --config <configuration file>)]
[-D <system properties>] [--group-id <group id>]
(-i <spec file> | --input-spec <spec file>)
[--import-mappings <import mappings>]
[--instantiation-types <instantiation types>]
[--invoker-package <invoker package>]
(-l <language> | --lang <language>)
[--language-specific-primitives <language specific primitives>]
[--library <library>] [--model-package <model package>]
[(-o <output directory> | --output <output directory>)]
[(-s | --skip-overwrite)]
[(-t <template directory> | --template-dir <template directory>)]
[--type-mappings <type mappings>] [(-v | --verbose)]
ONS
-a <authorization>, --auth <authorization>
adds authorization headers when fetching the swagger definitions
remotely. Pass in a URL-encoded string of name:header with a comma
separating multiple values
--additional-properties <additional properties>
sets additional properties that can be referenced by the mustache
templates in the format of name=value,name=value
--api-package <api package>
package for generated api classes
--artifact-id <artifact id>
artifactId in generated pom.xml
--artifact-version <artifact version>
artifact version in generated pom.xml
-c <configuration file>, --config <configuration file>
Path to json configuration file. File content should be in a json
format {"optionKey":"optionValue", "optionKey1":"optionValue1"...}
Supported options can be different for each language. Run
config-help -l {lang} command for language specific config options.
-D <system properties>
sets specified system properties in the format of
name=value,name=value
--group-id <group id>
groupId in generated pom.xml
-i <spec file>, --input-spec <spec file>
location of the swagger spec, as URL or file (required)
--import-mappings <import mappings>
specifies mappings between a given class and the import that should
be used for that class in the format of type=import,type=import
--instantiation-types <instantiation types>
sets instantiation type mappings in the format of
type=instantiatedType,type=instantiatedType.For example (in Java):
array=ArrayList,map=HashMap. In other words array types will get
instantiated as ArrayList in generated code.
--invoker-package <invoker package>
root package for generated code
-l <language>, --lang <language>
client language to generate (maybe class name in classpath,
required)
--language-specific-primitives <language specific primitives>
specifies additional language specific primitive types in the format
of type1,type2,type3,type3. For example:
String,boolean,Boolean,Double
--library <library>
library template (sub-template)
--model-package <model package>
package for generated models
-o <output directory>, --output <output directory>
where to write the generated files (current dir by default)
-s, --skip-overwrite
specifies if the existing files should be overwritten during the
generation.
-t <template directory>, --template-dir <template directory>
folder containing the template files
--type-mappings <type mappings>
sets mappings between swagger spec types and generated code types in
the format of swaggerType=generatedType,swaggerType=generatedType.
For example: array=List,map=Map,string=String
--reserved-words-mappings <import mappings>
specifies how a reserved name should be escaped to. Otherwise, the
default _<name> is used. For example id=identifier
-v, --verbose
verbose mode
You can then compile and run the client, as well as unit tests against it:
amples/client/petstore/java
package
Other languages have petstore samples, too:
n/android-petstore.sh
n/java-petstore.sh
n/objc-petstore.sh
It's just as easy–just use the -i flag to point to either a server or file.
Don't like the default swagger client syntax? Want a different language supported? No problem! Swagger codegen processes mustache templates with the jmustache engine. You can modify our templates or make your own.
You can look at modules/swagger-codegen/src/main/resources/${your-language} for examples. To make your own templates, create your own files and use the -t flag to specify your template folder. It actually is that easy.
If you're starting a project with a new language and don't see what you need, swagger-codegen can help you create a project to generate your own libraries:
-jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar meta \
output/myLibrary -n myClientCodegen -p com.my.company.codegen
This will write, in the folder output/myLibrary, all the files you need to get started, including a README.md. Once modified and compiled, you can load your library with the codegen and generate clients with your own, custom-rolled logic.
You would then compile your library in the output/myLibrary folder with mvn package and execute the codegen like such:
-cp output/myLibrary/target/myClientCodegen-swagger-codegen-1.0.0.jar:modules/swagger-codegen-cli/target/swagger-codegen-cli.jar io.swagger.codegen.SwaggerCodegen
For Windows users, you will need to use ; instead of : in the classpath, e.g.
-cp output/myLibrary/target/myClientCodegen-swagger-codegen-1.0.0.jar;modules/swagger-codegen-cli/target/swagger-codegen-cli.jar io.swagger.codegen.SwaggerCodegen
Note the myClientCodegen is an option now, and you can use the usual arguments for generating your library:
-cp output/myLibrary/target/myClientCodegen-swagger-codegen-1.0.0.jar:modules/swagger-codegen-cli/target/swagger-codegen-cli.jar \
.swagger.codegen.SwaggerCodegen generate -l myClientCodegen\
http://petstore.swagger.io/v2/swagger.json \
myClient
See our javascript library–it's completely dynamic and doesn't require static code generation. There is a third-party component called swagger-js-codegen that can generate angularjs or nodejs source code from a OpenAPI Specification.
:exclamation: On Dec 7th 2015, a Javascript API client generator has been added by @jfiala.
If you don't want to call your server, you can save the OpenAPI Spec files into a directory and pass an argument to the code generator like this:
/modules/swagger-codegen/src/test/resources/2_0/petstore.json
Great for creating libraries on your ci server, from the Swagger Editor… or while coding on an airplane.
You may not want to generate all models in your project. Likewise you may want just one or two apis to be written. If that's the case, you can use system properties to control the output:
The default is generate everything supported by the specific library. Once you enable a feature, it will restrict the contents generated:
nerate only models
-Dmodels {opts}
nerate only apis
-Dapis {opts}
nerate only supporting files
-DsupportingFiles
nerate models and supporting files
-Dmodels -DsupportingFiles
To control the specific files being generated, you can pass a CSV list of what you want:
nerate the User and Pet models only
dels=User,Pet
nerate the User model and the supportingFile `StringUtil.java`:
dels=User -DsupportingFiles=StringUtil.java
To control generation of docs and tests for api and models, pass false to the option. For api, these options are -DapiTests=false and -DapiDocs=false. For models, -DmodelTests=false and -DmodelDocs=false.
These options default to true and don't limit the generation of the feature options listed above (like -Dapi):
nerate only models (with tests and documentation)
-Dmodels {opts}
nerate only models (with tests but no documentation)
-Dmodels -DmodelDocs=false {opts}
nerate only User and Pet models (no tests and no documentation)
-Dmodels=User,Pet -DmodelTests=false {opts}
nerate only apis (without tests)
-Dapis -DapiTests=false {opts}
nerate only apis (modelTests option is ignored)
-Dapis -DmodelTests=false {opts}
When using selective generation, only the templates needed for the specific generation will be used.
Swagger codegen supports a .swagger-codegen-ignore file, similar to .gitignore or .dockerignore you're probably already familiar with.
The ignore file allows for better control over overwriting existing files than the --skip-overwrite flag. With the ignore file, you can specify individual files or directories can be ignored. This can be useful, for example if you only want a subset of the generated code.
Examples:
agger Codegen Ignore
nes beginning with a # are comments
is should match build.sh located anywhere.
d.sh
tches build.sh in the root
ld.sh
clude all recursively
/**
plicitly allow files excluded by other rules
s/UserApi.md
cursively exclude directories named Api
u can't negate files below this directory.
**/Api/
en this file is nested under /Api (excluded above),
is rule is ignored because parent directory is excluded by previous rule.
/**/PetApiTests.cs
clude a single, nested file explicitly
IO.Swagger.Test/Model/AnimalFarmTests.cs
The .swagger-codegen-ignore file must exist in the root of the output directory.
There are different aspects of customizing the code generator beyond just creating or modifying templates. Each language has a supporting configuration file to handle different type mappings, etc:
-1 modules/swagger-codegen/src/main/java/io/swagger/codegen/languages/
ractJavaJAXRSServerCodegen.java
ractTypeScriptClientCodegen.java
ScalaClientCodegen.java
oidClientCodegen.java
et5ServerCodegen.java
etCoreServerCodegen.java
cScalaClientCodegen.java
ClientCodegen.java
rpClientCodegen.java
ureClientCodegen.java
rpDotNet2ClientCodegen.java
ClientCodegen.java
hClientCodegen.java
kConnexionCodegen.java
ientCodegen.java
ellServantCodegen.java
erCodegen.java
CXFServerCodegen.java
ClientCodegen.java
InflectorServerCodegen.java
JerseyServerCodegen.java
ResteasyServerCodegen.java
scriptClientCodegen.java
JSServerCodegen.java
yFXServerCodegen
ClientCodegen.java
ClientCodegen.java
lientCodegen.java
onClientCodegen.java
PPGenerator.java
ClientCodegen.java
aClientCodegen.java
atraServerCodegen.java
xServerCodegen.java
traServerCodegen.java
FrameworkServerCodegen.java
ngMVCServerCodegen.java
icDocCodegen.java
icHtmlGenerator.java
gerGenerator.java
gerYamlGenerator.java
tCodegen.java
nClientCodegen.java
ScriptAngularClientCodegen.java
ScriptNodeClientCodegen.java
Each of these files creates reasonable defaults so you can get running quickly. But if you want to configure package names, prefixes, model folders, etc. you can use a json config file to pass the values.
-jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar generate \
http://petstore.swagger.io/v2/swagger.json \
java \
samples/client/petstore/java \
path/to/config.json
and config.json contains the following as an example:
piPackage" : "petstore"
Supported config options can be different per language. Running config-help -l {lang} will show available options.
**These options are applied via configuration file (e.g. config.json) or by passing them with -D{optionName}={optionValue}**. (If-D{optionName}` does not work, please open a ticket and we'll look into it)
-jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar config-help -l java
Output
IG OPTIONS
modelPackage
package for generated models
apiPackage
package for generated api classes
sortParamsByRequiredFlag
Sort method arguments to place required parameters before optional parameters. Default: true
invokerPackage
root package for generated code
groupId
groupId in generated pom.xml
artifactId
artifactId in generated pom.xml
artifactVersion
artifact version in generated pom.xml
sourceFolder
source folder for generated code
localVariablePrefix
prefix for generated code members and local variables
serializableModel
boolean - toggle "implements Serializable" for generated models
library
library template (sub-template) to use:
jersey1 - HTTP client: Jersey client 1.18. JSON processing: Jackson 2.4.2
jersey2 - HTTP client: Jersey client 2.6
feign - HTTP client: Netflix Feign 8.1.1. JSON processing: Jackson 2.6.3
okhttp-gson (default) - HTTP client: OkHttp 2.4.0. JSON processing: Gson 2.3.1
retrofit - HTTP client: OkHttp 2.4.0. JSON processing: Gson 2.3.1 (Retrofit 1.9.0)
retrofit2 - HTTP client: OkHttp 2.5.0. JSON processing: Gson 2.4 (Retrofit 2.0.0-beta2)
Your config file for Java can look like
roupId":"com.my.company",
rtifactId":"MyClient",
rtifactVersion":"1.2.0",
ibrary":"feign"
For all the unspecified options default values will be used.
Another way to override default options is to extend the config class for the specific language. To change, for example, the prefix for the Objective-C generated files, simply subclass the ObjcClientCodegen.java:
age com.mycompany.swagger.codegen;
rt io.swagger.codegen.languages.*;
ic class MyObjcCodegen extends ObjcClientCodegen {
static {
PREFIX = "HELO";
}
and specify the classname when running the generator:
om.mycompany.swagger.codegen.MyObjcCodegen
Your subclass will now be loaded and overrides the PREFIX value in the superclass.
Sometimes you don't want a model generated. In this case, you can simply specify an import mapping to tell the codegen what not to create. When doing this, every location that references a specific model will refer back to your classes. Note, this may not apply to all languages…
To specify an import mapping, use the --import-mappings argument and specify the model-to-import logic as such:
port-mappings Pet=my.models.MyPet
Or for multiple mappings:
my.models.MyPet,Order=my.models.MyOrder
You have options. The easiest is to use our online validator which not only will let you validate your spec, but with the debug flag, you can see what's wrong with your spec. For example:
http://online.swagger.io/validator/debug?url=http://petstore.swagger.io/v2/swagger.json
To do so, just use the -l dynamic-html flag when reading a spec file. This creates HTML documentation that is available as a single-page application with AJAX. To view the documentation:
amples/dynamic-html/
install
.
Which launches a node.js server so the AJAX calls have a place to go.
To do so, just use the -l html flag when reading a spec file. This creates a single, simple HTML file with embedded css so you can ship it as an email attachment, or load it from your filesystem:
amples/html/
index.html
Please refer to https://github.com/swagger-api/swagger-codegen/wiki/Server-stub-generator-HOWTO for more information.
This will create the swagger-codegen library from source.
package
Note! The templates are included in the library generated. If you want to modify the templates, you'll need to either repackage the library OR specify a path to your scripts
You can use the swagger-codegen-maven-plugin for integrating with your workflow, and generating any codegen target.
To push the auto-generated SDK to GitHub, we provide git_push.sh to streamline the process. For example:
1) Create a new repository in GitHub (Ref: https://help.github.com/articles/creating-a-new-repository/)
2) Generate the SDK
a -jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar generate \
modules/swagger-codegen/src/test/resources/2_0/petstore.json -l perl \
it-user-id "wing328" \
it-repo-id "petstore-perl" \
elease-note "Github integration demo" \
/var/tmp/perl/petstore
3) Push the SDK to GitHub
var/tmp/perl/petstore
/sh ./git_push.sh
One can also generate API client or server using the online generators (https://generator.swagger.io)
For example, to generate Ruby API client, simply send the following HTTP request using curl:
-X POST -H "content-type:application/json" -d '{"swaggerUrl":"http://petstore.swagger.io/v2/swagger.json"}' https://generator.swagger.io/api/gen/clients/ruby
Then you will receieve a JSON response with the URL to download the zipped code.
To customize the SDK, you can POST to https://generator.swagger.io/gen/clients/{language} with the following HTTP body:
ptions": {},
waggerUrl": "http://petstore.swagger.io/v2/swagger.json"
in which the options for a language can be obtained by submitting a GET request to https://generator.swagger.io/api/gen/clients/{language}:
For example, curl https://generator.swagger.io/api/gen/clients/python returns
ackageName":{
"opt":"packageName",
"description":"python package name (convention: snake_case).",
"type":"string",
"default":"swagger_client"
ackageVersion":{
"opt":"packageVersion",
"description":"python package version.",
"type":"string",
"default":"1.0.0"
ortParamsByRequiredFlag":{
"opt":"sortParamsByRequiredFlag",
"description":"Sort method arguments to place required parameters before optional parameters.",
"type":"boolean",
"default":"true"
To set package name to pet_store, the HTTP body of the request is as follows:
ptions": {
"packageName": "pet_store"
waggerUrl": "http://petstore.swagger.io/v2/swagger.json"
and here is the curl command:
-H "Content-type: application/json" -X POST -d '{"options": {"packageName": "pet_store"},"swaggerUrl": "http://petstore.swagger.io/v2/swagger.json"}' https://generator.swagger.io/api/gen/clients/python
Please refer to this page
Here are some companies/projects using Swagger Codegen in production. To add your company/project to the list, please visit README.md and click on the icon to edit the page.
Swagger Codegen core team members are contributors who have been making significant contributions (review issues, fix bugs, make enhancements, etc) to the project on a regular basis.
| Languages | Core Team (join date) |
|:————-|:————-|
| ActionScript | |
| C++ | |
| C# | @jimschubert (2016/05/01) | |
| Clojure | @xhh (2016/05/01) |
| Dart | |
| Groovy | |
| Go | @guohuang (2016/05/01) @neilotoole (2016/05/01) |
| Java | @cbornet (2016/05/01) @xhh (2016/05/01) @epaul (2016/06/04) |
| Java (Spring Cloud) | @cbornet (2016/07/19) |
| NodeJS/Javascript | @xhh (2016/05/01) |
| ObjC | @mateuszmackowiak (2016/05/09) |
| Perl | @wing328 (2016/05/01) |
| PHP | @arnested (2016/05/01) |
| Python | @scottrw93 (2016/05/01) |
| Ruby | @wing328 (2016/05/01) @zlx (2016/05/22) |
| Scala | |
| Swift | @jaz-ah (2016/05/01) @Edubits (2016/05/01) |
| TypeScript (Node) | @Vrolijkx (2016/05/01) |
| TypeScript (Angular1) | @Vrolijkx (2016/05/01) |
| TypeScript (Angular2) | @Vrolijkx (2016/05/01) |
| TypeScript (Fetch) | |
| Languages | Core Team (date joined) |
|:————- |:————-|
| C# ASP.NET5 | @jimschubert (2016/05/01) |
| Go Server | @guohuang (2016/06/13) |
| Haskell Servant | |
| Java Spring Boot | @cbornet (2016/07/19) |
| Java Spring MVC | @kolyjjj (2016/05/01) @cbornet (2016/07/19) |
| Java JAX-RS | |
| NancyFX | |
| NodeJS | @kolyjjj (2016/05/01) |
| PHP Lumen | @abcsum (2016/05/01) |
| PHP Silex | |
| PHP Slim | |
| Python Flask | |
| Ruby Sinatra | @wing328 (2016/05/01) | |
| Scala Scalatra | | |
| Scala Finch | @jimschubert (2017/01/28) |
Here is a list of template creators:
Here are the requirements to become a core team member:
rank within top 50 in https://github.com/swagger-api/swagger-codegen/graphs/contributors
to contribute, here are some good starting points
regular contributions to the project
about 3 hours per week
for contribution, it can be addressing issues, reviewing PRs submitted by others, submitting PR to fix bugs or make enhancements, etc
To join the core team, please reach out to wing328hk@gmail.com (@wing328) for more information.
To become a Template Creator, simply submit a PR for new API client (e.g. Rust, Elixir) or server stub (e.g. Ruby Grape) generator.
Swagger Codegen Evangelist shoulders one or more of the following responsibilities:
If you want to be a Swagger Codegen Evangelist, please kindly apply by sending an email to wing328hk@gmail.com (@wing328)
The Swagger Codegen project is intended as a benefit for users of the Swagger / Open API Specification. The project itself has the License as specified. In addition, please understand the following points:
When code is generated from this project, it shall be considered AS IS and owned by the user of the software. There are no warranties–expressed or implied–for generated code. You can do what you wish with it, and once generated, the code is your responsibility and subject to the licensing terms that you deem appropriate.
Copyright 2017 SmartBear Software
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
