Use qs stringify for post body #46
Open
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
Contributor
There was a problem hiding this comment.
would be nice to abstract these out a little with an object mapping content types to functions say something like:
exports.stringify['application/x-www-form-urlencoded'] = qs.stringify
so then we could have application/json etc
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.
This uses qs.stringify to turn options.body into a string if it is an object in Browser.post. I am not sure the best way to determine if a variable is an object so I used
Object.prototype.toString.call(options.body)(which I saw used in node-querystring (https://github.com/visionmedia/node-querystring/blob/master/lib/querystring.js#L17).