Skip to content

Minor improvements to the Lua client generator #6219

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

Merged
merged 2 commits into from
May 9, 2020
Merged

Minor improvements to the Lua client generator #6219

merged 2 commits into from
May 9, 2020

Conversation

wing328
Copy link
Member

@wing328 wing328 commented May 8, 2020

  • mark the generator as beta
  • minor code format
  • generate samples for OAS3 only

PR checklist

  • Read the contribution guidelines.
  • If contributing template-only or documentation-only changes which will change sample output, build the project before.
  • Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
  • File the PR against the correct branch: master, 4.3.x, 5.0.x. Default: master.
  • Copy the technical committee to review the pull request if your PR is targeting a particular programming language.

cc @daurnimator

@wing328 wing328 changed the title Minor improvement to Lua client generator Minor improvements to the Lua client generator May 8, 2020
@wing328 wing328 added this to the 5.0.0 milestone May 8, 2020
@wing328 wing328 merged commit d530405 into master May 9, 2020
@wing328 wing328 deleted the lua_update branch May 9, 2020 06:26
@@ -60,6 +60,10 @@ function pet_api:add_pet(pet)
--local var_content_type = { "application/json", "application/xml" }
req.headers:upsert("accept", "application/json")

-- TODO: create a function to select proper content-type
--local var_accept = { "application/xml", "application/json" }
req.headers:upsert("content-type", "application/xml")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're setting the content type to xml, but sending json.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right it's a known issue as mentioned in the code comment.

-- TODO: create a function to select proper content-type

As a workaround, users can rearrange the accepts to have application/json placed in the front.

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.

2 participants