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

[Elixir] Deserialize responses based on status code #2355

Merged
merged 15 commits into from
Mar 20, 2019

Conversation

mrmstn
Copy link
Contributor

@mrmstn mrmstn commented Mar 10, 2019

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, ./bin/openapi3/{LANG}-petstore.sh, ./bin/security/{LANG}-petstore.sh and ./bin/openapi3/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.4.x, 4.0.x. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language. cc: @wing328

Description of the PR

First of all, sorry if I might made some chaos. I branched this PR from the great work of @yknx4. I'm hoping the change history will look a little bit better after PR #2326 was merged.

With this PR the generated elixir client will be able deserialize a response based on the given statuscodes including the ability to match on a default response in case none of the give codes matches (https://swagger.io/docs/specification/describing-responses/)

This PR stops descriptions and doc parts from beeing escaped by mustache and will pin poison to ~> 3.0.0 since poison 4.0.0 doesn't seems to work right now (I haven't investigated anything)

based on #2326
closes #2334

@yknx4
Copy link
Contributor

yknx4 commented Mar 11, 2019

Thank you very much for keeping the work on this 👍

@mrmstn mrmstn marked this pull request as ready for review March 12, 2019 06:41
@mrmstn
Copy link
Contributor Author

mrmstn commented Mar 19, 2019

@wing328 could you also merge this PR tomorrow (Wed) ? After #2326

@wing328
Copy link
Member

wing328 commented Mar 19, 2019

@mrmstn 👌

@wing328
Copy link
Member

wing328 commented Mar 20, 2019

@mrmstn when you've time, I wonder if you can help resolve the merge conflicts.

@mrmstn
Copy link
Contributor Author

mrmstn commented Mar 20, 2019

@wing328 this should do the trick, the diff looks good to me now, let's see what the CI says

@DanielaIvanova
Copy link

@wing328 @mrmstn
Hi guys! I need these changes in my project, so, i would like to know when this PR will be approved and merged so i could continue working on it. I appreciate the work that you have done here.

@wing328 wing328 merged commit 49f3e9a into OpenAPITools:master Mar 20, 2019
@wing328
Copy link
Member

wing328 commented Mar 20, 2019

Just merged the PR into master.

Thanks for the contribution from @mrmstn

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.

[BUG][ELIXIR] deserialisation only happens when response has status 200
4 participants