chore(docs): add ability to generate xmldocs

[avodovnik]

This introduces a naive XmlDocs renderer for Markdown nodes. It needs to be called separately for now, i.e. the generateSourceCodeComment in Documentation doesn't integrate with it yet, but I'll add that somewhere down the line.

[pavelfeldman]

Why do we need to handle this edge case?

[avodovnik]

It's supposed to be a cheap way of getting rid of:

    /// <summary>
    /// </summary>

but instead of ignoring it, I might be better off outputting a warning as that means it's not documented.

[pavelfeldman]

It looks like md's list items differ from the xmldoc ones in a way that it wants a wrapping container. I would render lists as md, i.e. via prepending - . That'll erase this lastNode handling.

[avodovnik]

So, VS isn't smart enough to actually render that in a meaningful way. So I'll always need to wrap it in a <list> if I want it to display at least somewhat nicely to the end user.

This:

    /// <summary>
    /// Remember, that sometimes, you need to do the following:
    /// - Test 1
    /// - Test 2
    /// - Test 3
    /// - Test 4
    /// 
    /// But there are times, when you want to do
    /// <list type="bullet">
    /// <item><description>Something smart</description></item>
    /// <item><description>Something smarter</description></item>
    /// <item><description>The really smart thing</description></item>
    /// <item><description>Just a list</description></item>
    /// </list>
    /// Tis a thing <seealso 
    /// cref="Browser"/> test.
    /// <a href="https://www.google.com">This is a link.</a>
    /// </summary>

turns into this:

[pavelfeldman]

Give us some 2 space indents!

[avodovnik]

Fixed now... :-) Looks like my settings were wrong. Fixed that as well.

[pavelfeldman]

nit: we don't wrap single-liners with {}

[avodovnik]

I've mostly avoided doing that now, but then eslint seems to have thrown a fit. Either way, point taken, thanks!

[pavelfeldman]

Yeah, definitely don't use , your summary would actually read better without it.

[avodovnik]

I've reworked that code, so it's a bit more digestable, but I decided to keep using the li part for the reasons outlined above.

[pavelfeldman]

Sneaky! i like it!

[pavelfeldman]

probably const escapedText = escape(node.text) ?

[avodovnik]

I haven't ran into text I needed to escape, so I've omitted the escaping part for now.

[JoelEinbinder]

Code looks fine. I'd have some style nits, but I think they are all because this file is not covered by eslint. We should probably restore eslint for .js files or convert doclint to typescript.

[avodovnik]

@JoelEinbinder I reformatted using 2 space tabs, instead of 4, and I ran eslint hopefully fixing the majority of the nits. Hopefully this is approvable now, and I can improve it as I go along :-)