Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Promise<object> incorrectly renders as Promise<any> #656

Closed
tomc974 opened this issue Dec 6, 2017 · 4 comments
Closed

Promise<object> incorrectly renders as Promise<any> #656

tomc974 opened this issue Dec 6, 2017 · 4 comments
Labels
bug Functionality does not match expectation help wanted Contributions are especially encouraged
Projects
TypeScript Support

Comments

@tomc974
Copy link

tomc974 commented Dec 6, 2017

For example, if you define a type alias like this type T = Promise<object>, TypeScript (in VS Code) correctly displays the type of T as Promise<object> but TypeDoc will render it as Promise<any>.

TypeScript version: 2.6.1
TypeDoc: 0.9.0
@aciccarello
Copy link
Collaborator

May be related to #571 and #572

@aciccarello aciccarello added bug Functionality does not match expectation help wanted Contributions are especially encouraged labels Dec 6, 2017
@NaridaL NaridaL mentioned this issue Oct 5, 2018
Closed
@NaridaL
Copy link
Contributor

NaridaL commented Oct 8, 2018 •
edited

Should be fixed by microsoft/TypeScript#27608 (see microsoft/TypeScript#27583).

@aciccarello
Copy link
Collaborator

Great! I'll leave this open until we can confirm on a typescript nightly.

@NaridaL NaridaL mentioned this issue Oct 9, 2018
Merged
@aciccarello
Copy link
Collaborator

Confirmed that this was fixed upstream in #881.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Functionality does not match expectation help wanted Contributions are especially encouraged
Projects
No open projects
TypeScript Support
Awaiting triage
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tomc974 @NaridaL @aciccarello