Please allow jsdoc at function parameter

[Thaina]

Some function take complicate type such as function callback. I want to document it inline at the parameter but it seem salsa don't parse jsdoc there

[billti]

We don't support inline block comments currently. For now, you can always write multi-line block comments before the callback function, e.g.

[billti]

Note that placing an inline comment where you have it poses challenges if you have more than one parameter, as JsDoc @ tags are separated by newlines. The Google closure compiler does support just adding a type immediately before the parameter (e.g. function(/** number */ index){...}). We could consider that at a later point

[Thaina]

I see thank you

Confirmed I can do this

And this

[billti]

Great! Thanks. Interesting that I notice using the second form you show only works with a line break before the param. We should probably not require this (i.e. just allow it inline).

[evmar]

Note: Closure supports inline types as you mention, but in Closure, functions have other non-type "stuff" they worry about. For example optional params are written @param {number=} opt_foo and as far as I understand it you cannot use = in an inline type, it's specific to function params.

Another way of saying this is that /** X */ in Closure allows a type X, but @param {Y} is the parameter syntax Y which includes types but also optionality. I imagine (but haven't verified) that rest arguments (with ...) work similarly.

[aluanhaddad]

@martine I believe that optionality is indeed a type level concern.

[mhegazy]

Should be fixed in the next release of TypeScript TS 2.1.