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

Update to swagger-parser to 2.0.14-OpenAPITools.org-1 #3737

Merged
merged 4 commits into from
Aug 24, 2019

Conversation

jmini
Copy link
Member

@jmini jmini commented Aug 23, 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 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\. If contributing template-only or documentation-only changes which will change sample output, be sure to build the project first.
  • Filed the PR against the correct branch: master, 4.1.x, 5.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

Update the Swagger-Parser version to 2.0.14-OpenAPITools.org-1

Previous PR #3239

@auto-labeler auto-labeler bot added the WIP Work in Progress label Aug 23, 2019
@auto-labeler
Copy link

auto-labeler bot commented Aug 23, 2019

👍 Thanks for opening this issue!
🏷 I have applied any labels matching special text in your issue.

The team will review the labels and make any necessary changes.

pom.xml Outdated
@@ -271,6 +271,7 @@
</requireMavenVersion>
<requireReleaseDeps>
<message>No Snapshots Allowed!</message>
<onlyWhenRelease>true</onlyWhenRelease>
Copy link
Member Author

Choose a reason for hiding this comment

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

REMOVE THIS LINE when we switch to a released version!

@jmini
Copy link
Member Author

jmini commented Aug 23, 2019

The CI jobs looks good to me.

  • The samples must be update (when the schema is integer, the new version of swagger-parser/swagger-core adds a format -- this is making some internal default value explicit => OK for me)
  • Some CI services can not handle SNAPHSOT versions

I have just created the release:
https://github.com/OpenAPITools/swagger-parser/releases/tag/v2.0.14-OpenAPITools.org-1

It will appear on maven central soon.


I will update this PR when the jars are on Maven Central.

@jmini jmini removed the WIP Work in Progress label Aug 23, 2019
@jmini jmini changed the title [WIP] Update to swagger-parser to 2.0.14-OpenAPITools.org-1 Update to swagger-parser to 2.0.14-OpenAPITools.org-1 Aug 23, 2019
Copy link
Member

@JFCote JFCote left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -791,6 +791,7 @@ paths:
properties:
integer:
description: None
format: int32
Copy link
Member

Choose a reason for hiding this comment

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

I don't think these changes are related to the PR?

Copy link
Member

Choose a reason for hiding this comment

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

Oh I see you updated the samples, nevermind then!

Copy link
Member Author

Choose a reason for hiding this comment

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

I guess either Swagger-Parser is setting those (explicit default), or Swagger-Core has a new behavior.

IMO this is an acceptable change.

@jmini jmini mentioned this pull request Aug 24, 2019
4 tasks
@jmini jmini merged commit 286ddf3 into master Aug 24, 2019
@@ -726,6 +726,7 @@ paths:
properties:
integer:
description: None
format: int32
Copy link
Member

Choose a reason for hiding this comment

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

FYI. Our petstore (fake) spec does not specify the format. I think swagger parser now defaults format to int32 for integer type if no format is specified.

Not sure if the community welcomes this change. We'll see.

jimschubert added a commit that referenced this pull request Aug 25, 2019
* master: (45 commits)
  update python samples
  Two tiny fixes for Java Vertx client (#3683)
  Exclude "test" from packages so that it is not installed as top-level package when "pip installing" the generated sdk (#3731)
  [java-client] add unit test for JDK 11 HttpClient (#3735)
  [R] feat(r): handling error response for 3xx cases (#3571)
  [Dart] Avoid redundant null checking in fromJson (#3632)
  [core] Set isMultipart=true for multipart operations, fix possible NPE (#3750)
  reenable kotlin client tests in shippable ci (#3751)
  Fix null assignation to header/query param map (#3749)
  Mockito 3.0.0 (#3732)
  Update to swagger-parser to 2.0.14-OpenAPITools.org-1 (#3737)
  Add a link to a Qiita blog post (#3747)
  update csharp samples
  Simple spelling error in dotnet core comments (#3746)
  better support for multipart (#3736)
  [typescript-fetch] fix #1998: prefix req ifaces. (#3740)
  cpp-qt5-client: add valgrind memory test (#3663)
  [typescript-angular] Encode objects for multipart/form-data with json - fixes #2733 (#3738)
  [BUG] Https protocol schema is not handled correctly in java 11 native code #3729 (#3730)
  comment out kotlin client tests
  ...
@wing328 wing328 added this to the 4.1.1 milestone Aug 26, 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

3 participants