[JS] Add proper handle of 204 server response #4604
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
January 20, 2017 08:52
Used petstore-with-fake-endpoints-models-for-testing.yaml
Contributor
|
Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in https://github.com/swagger-api/swagger-codegen/graphs/contributors. Let me know if you need help fixing it. |
Contributor
|
@tharders your first PR looks very good 👍 I'll merge it after you fix the commit authorship. Have a nice weekend! |
wing328
changed the title
acramatte
added a commit
to comerge/swagger-codegen
that referenced
this pull request
Mar 7, 2017
* upstream/master: (261 commits) tests, fix for swagger-api#4647. Proper escaping project name per npmjs (swagger-api#4648) Add support for read-only values in spring model (swagger-api#4629) new batch file to exec all JS petstore batch files update JS petstore client Fix the `rm` to remove the correct file in two spring generation bash scripts (swagger-api#4630) fix for allowable values, swagger-api#4645 (swagger-api#4646) Issue 4637 Fix for ci build (swagger-api#4643) Added single quotes -- fixes bug where generated client throws an 'Uncaught Reference Error'. add https://pagertree.com/ add https://neverfail.com/ Removed pet variable from Javascript api_test Mustache file, which was undefined and is not necessary here. This should fix issue swagger-api#4608. (swagger-api#4624) Removed pet variable from Javascript api_test Mustache file, which was undefined and is not necessary here. This should fix issue swagger-api#4608. update ts angular2 petstore samples Enum constructFromObject should return value (swagger-api#4613) update js promise petstore sample Fix Issue 4554 - handle 204 server response in javascript (swagger-api#4604) Fix model prefix/suffix with incorrect camelization (swagger-api#4621) better handling of reserved words in models, operationId (swagger-api#4620) [java] Improve pom.xml to qualify for publishing to Maven central (swagger-api#4616) rebuilt samples ...
davidgri
pushed a commit
to davidgri/swagger-codegen
that referenced
this pull request
May 11, 2017
…i#4604) * issues 4554: Handle 204 response and handle deserialize exceptions * issue-4554: generate javascript client updated template Used petstore-with-fake-endpoints-models-for-testing.yaml * use petstore-with-fake-endpoints-models-for-testing.yaml like sh script
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated javascript ApiClient template to handle 204 server responses and handle exceptions in the deserialize method to ensure there are no uncaught exceptions.
This fixes the following issue
#4554
Note: I also updated the javascript-petstore.bat to use the petstore-with-fake-endpoints-models-for-testing.yaml like it is now in the shell script.