Gerrit Birkeland

I just realized, this is at least very closely related to #6, more probably a duplicate, but I'll leave that choice to the maintainers.

> Is there ever a legitimate reason to have two TDoc comments for the same API item? I don't believe there is, I've always found the compiler's behavior confusing. However,...

It seems odd to me that `@throws` is before `@param`s / `@returns`, otherwise this looks reasonable to me and how I would write it naturally. --- Broken tag: @rbuckton FYI

`@eventProperty` supports one style of events, and while the type of event it describes is common in the C# land, it does not capture all common patterns in JS/TS. Node...

Sorry for the delay here, TypeDoc uses `@event` to place members tagged with it under a separate heading.  https://typedoc.org/api/classes/converter.html --- Yes, there's a clever way to describe the events...

This is next on my todo list once library mode (#1184) is done, but unfortunately I only have a couple hours a week to work on this project...

This is a similar request to #1513. I think this might make sense to do - with some limitations. 1. This should only happen if the type alias has no...

This is expected behavior right now. We don't have custom rendering to try to pretty print any types. It isn't just object types either, https://typedoc.org/api/modules.html#KeyToDeclaration is less than useful... I...

I'll leave this open until I've confirmed it's resolved :)

Still think I'm going to regret it, but it's coming in... will see how this goes.