Pete Gonzalez

An inline tag seems like a better design, since it clearly conveys that we want a small text string that shouldn't contain any markup: ```ts /** * The Widget class....

@Rick-Kirkham The basic idea here is that TSDoc is supposed to have a standard grammar for documentation tags. The 3 kinds of tags are: - block tags (e.g. `@remarks` or...

@dend FYI

JQuery seems to track three version: - Version when the API was **added** - Version when it started being **deprecated** - Version when it was finally **removed** It seems like...

Hmm... In the current implementation, `DeclarationReference.parse('a.b c.d').toString()` outputs `"a.b c.d"`.

@DanielRosenwasser

Alternatively, if we wanted to follow the model of JSON schemas, it might go like this: In your package.json file, you would register a custom TSDoc schema: ```json { "name":...

I started prototyping this idea today. If we go this route, it will be a major simplification and should save us a lot of time on the implementation.

@sharwell thanks for your feedback here. As I mentioned in the initial issue description, TSDoc and Markdown have somewhat different requirements, which greatly complicates attempts to embed Markdown inside TSDoc....

Right, Monaco's default styler implements a scanner that recognizes various constructs that are commonly found in JavaScript/TypeScript doc comments. Of course, other editors like WebStorm may parse these comments differently....