You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/** * Here is some documentation. */exportconstf=()=>{};/** * Here is some documentation */exportfunctiong(){}
Commit d1be956 changed how this is handled. If I checkout the commit before it e30ed7a, run npm ci && npm build and then run typedoc on this file, the rendering of f and g are indistinguishable:
On d1be956 the output changed so that the comment is above f. The output for g is unchanged:
The text was updated successfully, but these errors were encountered:
This was intended at the time, though I'm less certain that it was a good idea after living with it for a while... The intent at the time was for const fn = () => 123 to be treated in the same way type Fn = () => 123 would be, where the comment doesn't belong to the signature, but to the function/type alias that owns the signature.
Consider the following source:
Commit d1be956 changed how this is handled. If I checkout the commit before it e30ed7a, run
npm ci && npm build
and then run typedoc on this file, the rendering off
andg
are indistinguishable:On d1be956 the output changed so that the comment is above
f
. The output forg
is unchanged:The text was updated successfully, but these errors were encountered: