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

[TypeScript] Take the modelPropertyNaming property into account again #7202

Merged
merged 1 commit into from
Dec 21, 2017
Merged

[TypeScript] Take the modelPropertyNaming property into account again #7202

merged 1 commit into from
Dec 21, 2017

Conversation

JFCote
Copy link
Contributor

@JFCote JFCote commented Dec 18, 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.

@TiFu (2017/07) @taxpon (2017/07) @sebastianhaas (2017/07) @kenisteward (2017/07) @Vrolijkx (2017/09)

Description of the PR

Fix for #7201.

@TiFu
Copy link
Contributor

TiFu commented Dec 18, 2017

@JFCote did you verify that it fixes #7201?
If not:
@gennadiylitvinyuk can you confirm that this fixes the issue?

@gennadiylitvinyuk
Copy link

@TiFu Sorry, I can't compile Java right now, but the changes are looking good for me.

@JFCote
Copy link
Contributor Author

JFCote commented Dec 18, 2017

@TiFu I did not have time to do the validation. I just wanted to provide a quick fix but I'm pretty confident that it should work. There was no sample using this parameter and nothing has changed when running the samples so at least, it didn't break anything.

If I have time later this week, I will test it. Otherwise, if someone here with the right setup can test it, that would be nice :)

Thanks

@yobryon
Copy link
Contributor

yobryon commented Dec 20, 2017

Tested with a build against PR 7202 and it does honor the modelPropertyNaming option again.

Copy link
Contributor

@TiFu TiFu left a comment

Choose a reason for hiding this comment

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

Thanks for testing! @yobryon
Looks good to me then.

@wing328 wing328 merged commit 572bafe into swagger-api:master Dec 21, 2017
@wing328 wing328 changed the title Fix for #7201: Take the modelPropertyNaming property into account again [TypeScript] Take the modelPropertyNaming property into account again Dec 21, 2017
@JFCote JFCote deleted the fix-7201 branch December 21, 2017 15:23
slarti-b added a commit to slarti-b/swagger-codegen that referenced this pull request Dec 26, 2017
* master:
  move bvwells to go tech comm
  update current stable version in readme
  skip push snapshot to avoid error
  comment out checkstyle in circleci pom.xml
  comment out check style plugin
  Revert "update version to 2.4.0-SNAPSHOT"
  update ci config to install codegen locally
  update doc to 2.3.0
  update version to 2.4.0-SNAPSHOT
  update version to 2.3.0
  fix net35 with JsonSubTypes (swagger-api#7043)
  [Javascript] Set ES5 as default (swagger-api#7239)
  swagger-api#7201: Take the modelPropertyNaming property into account again (swagger-api#7202)
  add trenneman as elm creator
  add bvwells to go technical committee
  Video "Building an API with Swagger" (swagger-api#7237)
  [Akka-Scala] This is a fix to a bug introduced by this PR swagger-api#7172 (swagger-api#7228)
  Add Elm language - BETA (swagger-api#6947)
  bump stack resolver to lts-10.0 (swagger-api#7221)
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

5 participants