Skip to content

Conversation

@fMads
Copy link
Contributor

@fMads fMads commented Dec 8, 2017

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: 3.0.0 branch for changes related to OpenAPI spec 3.0. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.
    @jebentier (2017/07) @dkarlovi (2017/07) @mandrean (2017/08) @jfastnacht (2017/09) @ackintosh (2017/09)

Description of the PR

Fixed issue #7137 by checking Response before calling getBody() when catching ApiException

@ackintosh
Copy link
Contributor

Nice catch! LGTM 👍
Please run ./bin/php-petstore.sh, ./bin/security/php-petstore.sh to update the PHP client samples.

@wing328
Copy link
Contributor

wing328 commented Dec 9, 2017

Tests with updated PHP Petstore client passed via https://travis-ci.org/swagger-api/swagger-codegen/builds/313889523

@wing328 wing328 merged commit 2af8868 into swagger-api:master Dec 9, 2017
@wing328
Copy link
Contributor

wing328 commented Dec 9, 2017

@fMads thanks for the contributing the fix.

@ackintosh thanks for reviewing the PR.

Gingonic pushed a commit to wirelane/swagger-codegen that referenced this pull request Dec 9, 2017
@wing328 wing328 changed the title Fixed #7137 by checking for Response before calling getBody() on it [PHP] checking for Response before calling getBody() on it Dec 12, 2017
@wing328 wing328 added this to the v2.3.0 milestone Dec 12, 2017
@fMads fMads deleted the issue_7137 branch May 9, 2018 06:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants