Can't use optionnal parameter in Router @:post

[ErikRikoo]

If I am using a @:post Root with optionnal parameter like:

@:post('/send-mail')
public function sendMail(body:{name:String, ?subject:String}):HttpStatusCode {
    trace(body);
    return OK;
}

I get on client side:

{
   code: 422
   data: {"error":"missing field "subject" at characters 0 - 14}
   message: "Unprocessable Entity"
}

When giving: {"name":"bar\"}

The issue is fixed if I am passing an empty string to it, so it seems that it is the optionnal parameter feature that is not working

[kevinresol]

Your case should be handled now. But we still need to work out the more complex case where the object wrapper itself is optional. This might possibly be forbidden except for keyword objects.

example (allow):

@:post
function(?body:{foo:String, ?bar:Int})

example (disallow):

@:post
@:params(obj.foo = query['foo'], obj.bar = body['bar'])
function(?obj:{foo:String, ?bar:Int})

with error like: argument "obj" cannot be optional because it contains multiple parameter sources