Function with properties shown as variable

[y-nk]

Search terms

Functions type property

Expected Behavior

Functions should be listed as functions

Actual Behavior

Steps to reproduce the bug

// will be seen as function in typedoc
const foo = () => {}

// will be seen as variable in typedoc
const bar = () => {}
bar.metadata = "baz"

Environment

• Typedoc version: latest
• TypeScript version: latest

[Gerrit0]

This happens because it isn't caught as a special case in the converter

typedoc/src/lib/converter/symbols.ts

Lines 771 to 773 in 9d84e2e

	if (type.getCallSignatures().length && !type.getProperties().length) {
	return convertVariableAsFunction(context, symbol, exportSymbol);
	}

Fixing it would involve updating that to also create a namespace for any properties.

Workaround:

const bar = () => {}
namespace bar {
  export const metadata = "baz"
}

[Gerrit0]

Note: Should probably do this only if the extra properties are defined with a PropertyAccessExpression. It would make #1735 worse to do it in every case.

[Gerrit0]

Apparently some TS version changed how symbol flags were set, because in TS 4.7.2, with no code changes, the following gets converted as a variable and a namespace.

const bar = () => {}
bar.metadata = "baz"

I'm going to go ahead and make the change to convert a variable as a function if it contains any call signatures... hopefully it doesn't make worse documentation in some edge case I'm not thinking of right now.

[y-nk]

@Gerrit0 thank you for the long-term follow-up this is highly appreciated. 🙏