Skip to content

[Ruby] Fix typo in description#4624

Merged
wing328 merged 1 commit intoOpenAPITools:masterfrom
jirikuncar:patch-1
Nov 28, 2019
Merged

[Ruby] Fix typo in description#4624
wing328 merged 1 commit intoOpenAPITools:masterfrom
jirikuncar:patch-1

Conversation

@jirikuncar
Copy link
Copy Markdown
Contributor

@jirikuncar jirikuncar commented Nov 27, 2019

Simple typo in Ruby client.

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 @cliffano (2017/07) @zlx (2017/09) @autopp (2019/02)

@autopp
Copy link
Copy Markdown
Contributor

autopp commented Nov 27, 2019

@jirikuncar Thanks for PR!
Cound you run bin/ruby-client-petstore.sh, bin/openapi3/ruby-client-petstore.sh and bin/openapi3/ruby-client-faraday-petstore.sh to update samples and commit changes?

@jirikuncar
Copy link
Copy Markdown
Contributor Author

jirikuncar commented Nov 27, 2019

I can try. It would be nice if the CI creates a patch and submits a PR.

@wing328
Copy link
Copy Markdown
Member

wing328 commented Nov 28, 2019

No worry. I'll update the samples after merging this PR.

Thanks for the PR.

@wing328
Copy link
Copy Markdown
Member

wing328 commented Dec 2, 2019

@jirikuncar jirikuncar deleted the patch-1 branch December 2, 2019 09:32
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