Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix NPE in body parameter due to incorrect parameter/consume #563

Merged
merged 1 commit into from
Jul 14, 2018

Conversation

wing328
Copy link
Member

@wing328 wing328 commented Jul 14, 2018

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

After #383, a NPE will occur if form parameter is defined and consumes is set to applicataion/json.

This PR will fix the problem.

Tested with the spec in #383 (comment) as well.

Follow-up: add a test case to fake petstore to catch the issue moving forward.

@wing328 wing328 changed the title fix NPE in body parameter due to incorrect parameter/consume Fix NPE in body parameter due to incorrect parameter/consume Jul 14, 2018
@wing328 wing328 added this to the 3.1.1 milestone Jul 14, 2018
@wing328 wing328 merged commit df81534 into master Jul 14, 2018
@wing328 wing328 deleted the fix_npe_body branch July 20, 2018 09:48
A-Joshi pushed a commit to ihsmarkitoss/openapi-generator that referenced this pull request Feb 27, 2019
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.

None yet

1 participant