-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exported generic types do not resolve their type parameters #156
Comments
Hi, thank you for your message. Type aliases are quite difficult to document as the compiler resolves them very early in the process so TypeDoc has to follow some thin hints to resolve them. I'll add this as an enhancement and will try to check back on it if I find the time. |
Great, thanks! Date: Tue, 8 Dec 2015 11:41:50 -0800 Hi, thank you for your message. Type aliases are quite difficult to document as the compiler resolves them very early in the process so TypeDoc has to follow some thin hints to resolve them. I'll add this as an enhancement and will try to check back on it if I find the time. — |
Hey! I wonder if the ~3 years that have passed have changed something in it in terms of TypeScript tooling? The following code has conditional types in it, but the TS server types it correctly; however, TypeDoc wouldn't "resolve" the type. This type is hand-rolled, but you can easily see how a It is something that can be done? Is it something you are willing to support? |
Came here looking for support for export interface RTPMediaExtensions extends Pick<RTCPeerConnection,
| 'getSenders'
| 'getReceivers'
| 'getTransceivers'
| 'addTrack'
| 'removeTrack'
| 'addTransceiver'
| 'addEventListener'
| 'removeEventListener'
| 'ontrack'
> {} With "Inherited" on, I am looking for the Interface's documentation to show these picked properties -- but instead it's an empty interface in typedoc's output. Not sure where to start looking in TypeDoc for solving this though. |
… previously Pick<>'d for better TypeDoc support: See TypeStrong/typedoc#156 (comment) for more information.
… previously Pick<>'d for better TypeDoc support: See TypeStrong/typedoc#156 (comment) for more information.
Closing in favor of #1386 - this is fixed in 0.20. |
For the below example:
The documentation shows:
someProperty: Z
and
How do I get it to show:
and something like:
The text was updated successfully, but these errors were encountered: