Skip to content
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

Non-string parameters should be stringified #14

Closed
64bits opened this issue Nov 19, 2015 · 0 comments
Closed

Non-string parameters should be stringified #14

64bits opened this issue Nov 19, 2015 · 0 comments

Comments

@64bits
Copy link

64bits commented Nov 19, 2015

Currently if an object is passed in params, e.g.:

{
    attachments: {
        pretext: "some text",
        fields: ...
    }
}

It just doesn't work. The reason is that the object needs to be stringified. This module should run JSON.stringify on such (or all non-string) objects automatically, given that all param values must necessarily be strings.

mishk0 pushed a commit that referenced this issue Nov 20, 2015
@mishk0 mishk0 closed this as completed Nov 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants