[BUG] Using TypeScript utility types breaks the generated type in documentation.json

[TomONeill]

Overview of the issue

Using TypeScript utility types like Uncapitalize<> results in a literal string in the documentation.json of said utility type, instead of the compiled type.

Operating System, Node.js, npm, compodoc version(s)

Windows 11 Enterprise (23H2)

Node v20.9.0
npm 10.2.4

@compodoc/compodoc@1.1.22

Compodoc installed globally or locally ?

Locally

Motivation for or Use Case

We're using Storybook together with Compodoc and since we're also using utility types like Uncapitalize in several instances, this results in the Controls being unable to propagate the right type/value.

Reproduce the error

1. Create a class with either a property or method with a utility type (like Uncapitalize).

@Injectable({
    providedIn: 'root'
})
export class MyService {
    public myMethod(myParam: Uncapitalize<"ExampleA" | "ExampleB">): void {
    }
}

2. Run compodoc

Result:

{
    "name": "MyService",
    "id": "injectable-MyService-xxxx",
    "file": "xxx/src/lib/my.service.ts",
    "properties": [],
    "methods": [
        {
            "name": "myMethod",
            "args": [
                {
                    "name": "myParam",
                    "type": "Uncapitalize<>",
                    "deprecated": false,
                    "deprecationMessage": ""
                }
            ]
        }
    ]
}

note that the result was modified to better point out the issue

Notice how type literally has string Uncapitalize with an empty generic. I expected "exampleA" | "exampleB" as type.

Related issues

#1329

But in this issue another problem is pointed out (keyof typeof) even though it relates to the problem pointed out in this issue.

Suggest a Fix

-