Created by: Peaches491
PR checklist
-
Read the contribution guidelines. -
Ran the shell script under ./bin/
to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.sh
and./bin/security/{LANG}-petstore.sh
if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\
. -
Filed the PR against the correct branch: master
,3.1.x
,4.0.x
. Default:master
. -
Copied the technical committee to review the pull request if your PR is targeting a particular programming language.
Description of the PR
Currently, all executions of openapi-generator
produce a set of supportingFiles
alongside the model/
and api/
files. If you have more than one openapi-generator
spec target, these supportingFiles
are completely identical, except for the namespace in which they are generated.
This PR allows users to specify supportingFilesDirectory
and supportingFilesNamespace
, the two parameters necessary to point the generated model/*
and api/*
files to an external set of supportingFiles
.
This enables the end-user to create useful tooling around this common set of supportingFiles
.
Left unset, the generated code is nearly equivalent to that in master
.