- 
  Notifications
 
You must be signed in to change notification settings  - Fork 6k
 
[JavaScript] Encode form paramerers properly #4836
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
 
  Merged
 
 
 wing328
 merged 1 commit into
 swagger-api:master 
from
hamedrnik:js-client-post-form-encoding 
 
 
 
  
 Mar 3, 2017 
 
 
 
  Merged
 
 [JavaScript] Encode form paramerers properly #4836
 wing328
 merged 1 commit into
 swagger-api:master 
from
hamedrnik:js-client-post-form-encoding 
 
 
 
  
 Mar 3, 2017 
 
 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
 
 
 
 
 Superagent doesn't encode form parameters properly. For example it doesn't encode objects which contain array. The following is a failed test case:
var my_opts = {
 'storyId': 65441,
 'id': [56, 352]
};
 @IceAge thanks for the PR, which has been merged into master.
 
 @wing328
wing328
 changed the title
(削除) Encode form paramerers properly (削除ここまで)
(追記) [JavaScript] Encode form paramerers properly (追記ここまで)
 Mar 12, 2017 
 
 
 
 spr3nk3ls 
 pushed a commit
 to spr3nk3ls/swagger-codegen
 that referenced
 this pull request
 
 Mar 28, 2017 
 
 
 
 
 
 
 
 
Superagent doesn't encode form parameters properly. For example it doesn't encode objects which contain array. The following is a failed test case:
var my_opts = {
 'storyId': 65441,
 'id': [56, 352]
};
 
 
 Sign up for free
 to join this conversation on GitHub.
 Already have an account?
 Sign in to comment
 
 
 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.
 
 
 
 
PR checklist
./bin/to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.shand./bin/security/{LANG}-petstore.shif updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates)2.3.0branch for breaking (non-backward compatible) changes.Description of the PR
Superagent doesn't encode form parameters properly. For example it doesn't encode objects which contain array. The following is a failed test case: