Remove tsdocs from documented const initialisers

[knoan]

• I have checked issues with bug label and found no duplicates

Steps to reproduce the bug

Generate docs for the following snippet:

export const Work={

	/**
	 * Lorem ipsum
	 */
	a: "one" as string,

	/**
	 * Sit amet
	 */
	b: 2 as number

} as const;

tsconfig.json

{
	"typedocOptions": {
		"mode": "modules",
		"theme": "minimal",
		"out": "docs"
	}
}

Expected Behavior

tsdocs not included in documented const initialiser, i.e.

Work: { a: string; b: number } = { a: "one", b: 2 } as const

Actual Behavior

tsdocs included verbatim in documented const initialiser, i.e.

Environment

• Typedoc version: 0.16.11
• Node.js version: v11.10.0
• OS: macOS 10.15.3

[Gerrit0]

This happens here:

typedoc/src/lib/converter/convert-expression.ts

Lines 19 to 34 in d18664d

	export function convertExpression(expression: ts.Expression): string {
	switch (expression.kind) {
	case ts.SyntaxKind.StringLiteral:
	return '"' + (<ts.LiteralExpression> expression).text + '"';
	case ts.SyntaxKind.NumericLiteral:
	return (<ts.LiteralExpression> expression).text;
	case ts.SyntaxKind.TrueKeyword:
	return 'true';
	case ts.SyntaxKind.FalseKeyword:
	return 'false';
	case ts.SyntaxKind.NullKeyword:
	return 'null';
	default:
	return expression.getText(expression.getSourceFile());
	}
	}

I think it should be possible to ask TS for a printer configured to remove comments and use that instead of getText. PR welcome if you'd like to give it a shot. I probably won't get to it for a while.

[Gerrit0]

0.20.1 renders this as:

In investigating other issues with the initializers, I decided that showing complex values was mostly not useful, so now only a few detected "simple" expressions are shown.