[Golang][client] delete sample output dir before rebuild #477
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR checklist
./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\
.master
,3.1.x
,4.0.x
. Default:master
.@antihax
@bvwells
Description of the PR
This deletes the sample Go client output dir
samples/client/petstore/go/go-petstore
before rebuilding the sample withbin/go-petstore.sh
.Benefits:
Of note, this PR currently results in the deletion of the Swagger 2.0 spec at:
samples/client/petstore/go/go-petstore/api/swagger.yaml
The 3.0.1 OpenAPI spec remains at:
samples/client/petstore/go/go-petstore/api/openapi.yaml
If we want to keep the Swagger 2.0 spec, it seems like may be worth looking into the
postProcessSupportingFileData
inAbstractGoCodegen.java
and related methods inDefaultGenerator.java
.