deno_doc

Now, it doesn't render JSDoc tag for classes' constructors. When to run with file: new A(); const a = new A(); a.method(); It can see 's example but it cannot see 's example. No route for It can see 's example at

It would be great to generate clickable anchors alongside the headers For example, instead of generate Where `#` at the least from the header. (got this particular format from VitePress).

When exporting a function expression, I can annotate its types on the expression's parameters and return, or on the exported symbol by declaring it to be a function with the same parameters and return. In the latter case, since I specified the return type in the variable's type annotation, I expect that to satisfy the explicit return types requirement, which it does for the isolatedDeclarations compiler option. However, arrow functions still raise a lint error unless I also add the return type, while some function expressions don't raise an error even with no expression or declaration types. Expected behavior: isolatedDeclarations errors on the un-annotated a1/b1 and a3/b3, but allows a2/b2 because its type is inferrable. Following that seems reasonable, or perhaps requiring annotations for a2/b2 as well if this tool doesn't want to do that inference. I also don't expect differences between arrow functions and function expressions. Actual behavior: a1/a3/b3, raise the missing-return-type error as expected. b1 satisfies the checker despite not having any type annotations. a5 fails without the additional return type in a6, but b5 is just fine.