This would be nice.
On Wednesday, 21 May 2014 12:45:47 UTC+1, Charles Pick wrote:
>
> yes sounds good, should also support the normal
> application/x-www-form-urlencoded
> mime type, so the client can POST data like:
>
> params[foo]=foo¶ms[bar]=bar
>
> and the server would convert into:
>
> {
>
yes sounds good, should also support the normal
application/x-www-form-urlencoded
mime type, so the client can POST data like:
params[foo]=foo¶ms[bar]=bar
and the server would convert into:
{
params: {
foo: 'foo',
bar: 'bar'
}
}
which will make it easier to test with standard tooli
Hi Thomas,
we could support passing a JSON as payload of POST operation with a JSON
that will be bound to params. Example:
{ "a" : 3, "b" : "Jill" }
And in my function I'll find the 2 params a and b bound with such value.
Charles is working to the new HTTP Api, WDYT Charles about it?
Lvc@
On
JSON.parse fixed this.
On Tuesday, 20 May 2014 23:40:36 UTC+1, Thomas Kennedy wrote:
>
> I have a server side with javascript function one parameter called Data.
>
> The value of Data is {"test":5}. This is passed in as a string.
>
> in the javascript function I want to access the value of test
