-
Notifications
You must be signed in to change notification settings - Fork 6k
Fixes #646: Example field handling has been fixed. #676
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -440,7 +440,7 @@ | |
<swagger-parser-version>1.0.6-SNAPSHOT</swagger-parser-version> | ||
<scala-version>2.10.4</scala-version> | ||
<felix-version>2.3.4</felix-version> | ||
<swagger-core-version>1.5.1-M2</swagger-core-version> | ||
<swagger-core-version>1.5.2-M2-SNAPSHOT</swagger-core-version> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @tomtit - notice that this broke the build There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @webron, that is why I've referenced the swagger-api/swagger-core/pull/1002 pull request. The com.wordnik.swagger.models.Response from that change is required. Just don't know how to reference the develop_2.0 branch properly. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Apologies, I had missed that comment. We can't depend on a SNAPSHOT here though. That means we'll have to wait until swagger-core is released and then modify this PR accordingly. Still not sure what version that's going to end up being. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @tomtit There is a Java generator that uses examples but the code cannot be merged back to the official repo as the generated code is in Java 8 but swagger-codegen has to be built in Java 7 container. |
||
<scala-test-version>2.1.4</scala-test-version> | ||
<commons-io-version>2.3</commons-io-version> | ||
<commons-cli-version>1.2</commons-cli-version> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This piece has to be reworked as it renders examples into JSON view regardless of the
contentType
value.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tomtit I would recommend you to leave a comment (TODO) in the code so that someone can find out what needs to be done and potentially file a PR for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wing328, I would like to rework this piece as a part of this PR. I realized the problem with
contentType
after the PR had been created. Perhaps @fehguy or @webron could provide some additional comments here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is the note from discussion with @webron:
So, the proposed changes provide exactly this functionality.