Expose response.statusText in the response out object #241
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
fehguy
added a commit
that referenced
this pull request
Feb 19, 2015
Expose response.statusText in the response out object
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.
Hi there,
Currently, there is no way to obtain the statusText from the response in the response handlers. In our case, we have a need for this as we have meaningful statusText that we need to act upon. This pull request adds response.statusText to the response out object to expose meaningful statusText.
I refrained from generating the lib/swagger-client.js and lib/swagger-client.min.js files. If you could forward-port it to the master branch, this would be great.
Let me know if there is anything additional I can do!
Thanks for your hard work and great library!