Gerrit Birkeland

This isn't a TSDoc problem. It's a JavaScript problem. JavaScript (and therefore TypeScript) does not support nested block comments, so the whole comment ends at `'some output' */`

One concern I have: This new form of declaration references appears to be incapable of supporting the [`{@label}`](https://tsdoc.org/pages/tags/label/) tag. https://github.com/microsoft/tsdoc/blob/b7bddc1ceb6b6759857c66ef3af6e5e95655fb8c/tsdoc/src/beta/DeclarationReference.grammarkdown#L157-L161

It sounds like you are after JSDoc with the `commentsOnly` plugin. https://github.com/jsdoc/jsdoc/blob/master/plugins/commentsOnly.js

```ts let person = new Person(); // MISTAKE: person.update({ name: undefined, //

The first two bullet points sound like an ideal solution to me. The lax mode change makes sense, but if I wrote a comment after a tag (that I didn't...

Given that you are using TypeDoc, you'll need to write a TypeDoc plugin rather than a TSDoc plugin (which isn't a thing) You could do this by listening to `Converter.EVENT_CREATE_DECLARATION`...

This isn't one of the goals of TSDoc. TSDoc only describes how comments ought to be parsed, and it leaves generating documentation up to tools which implement the TSDoc spec....

@WesleyMConner, considering I've been maintaining it for the past few years... yes ;) it's goals, however, do not always align with those running the TSDoc project. It's mostly compatible now,...

> Thus I'd propose that TSDoc omit this aspect and instead require an explicit `{@link}` for any hyperlinks with `@see`. This is exactly the behavior I would expect from TSDoc...

The playground already strips HTML tags from the output and includes only their text. I tried including `alert(1)` and `alert(1)` was displayed. It looks like the security issue should be...