Pete Gonzalez

Since this is an RFC, let's keep this issue open. All the RFC issues will get closed when the formal spec is completed.

Not yet, but we've been wanting to make one! Want to propose a design?

@micthiesen brought up the same question in #228. The first step is to agree on a design: How would the rule work? (Does it check every class/member/function? Only exported ones?...

> Would starting out with a basic non-empty content requirement be sufficient? Sure, although I think the more interesting design question is around *which* things need comments. Fantasizing for a...

> In our case, class constructors can sometimes get complex making docs on constructors that require arguments a potential need Seems reasonable. By the way, we generally solve this by...

We started to work on this before. If I remember right there was a security concern where TSDoc can contain HTML tags which could contain executable scripts, so we would...

> The playground already strips HTML tags from the output and includes only their text. It doesn't really "strip" them. They simply aren't emitted yet (again because we realized there...

@KevinTCoughlin FYI (who I think originally proposed the code-sharing query parameter)

From a documentation perspective, TSDoc's design seems a little better to me: - It allows you to explain your example using rich text English, and possibly present more than one...

> I appreciate that while trying to set a new standard there might be a transitionary period during which things are messed up. I just hope that VSCode and TSDoc...