-
Notifications
You must be signed in to change notification settings - Fork 710
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
Support for TypeScript 4.2.2 #1517
Support for TypeScript 4.2.2 #1517
Comments
npm actually errors on peer dependencies with unsupported versions now?! When did that happen? I gave upgrading a shot, but it looks like 4.2 has caused some regressions that will take some more investigation to sort out... I should be able to put a release out this weekend at the latest. |
Starting with version 7, npm has a more consistent handling of peer dependencies. |
Hmm.. well, this is problematic. TS 4.2 has said "TypeDoc's type conversion structure is inherently flawed" TypeDoc's current structure assumes that converting a type to a type node to determine how to convert it is a reasonable approach - and it does work for a lot of cases!... but it doesn't work everywhere. The test that's failing when updating to TS 4.2 is this one: export class TestClass {
a: string;
b: number;
}
export class GenericClass<T extends keyof TestClass> {
c: T;
} Particularly, when converting the constraint of type parameter of the The type converter then gets confused since it assumes that since TS gave us a type operator type node the type must be a type operator type, tries to access a property which doesn't exist, and converts the operated type to new <T extends keyof any>() => GenericClass<T> Properly fixing this is annoying, since it means ripping apart the type converter. I'm in the middle of moving this weekend, so I might not have time to finish it until next weekend. |
Thank you for caring and good luck with the moving. |
Well, I'm nearly there. Turns out that with just a bit of poking at internals, I can make the existing converter keep working. CI is very unhappy with me since prettier doesn't support abstract signatures yet, but publishing manually did the trick. |
Search Terms
TypeScript 4.2.2
Problem
Unable to use TypeScript 4.2.2
Suggested Solution
Support TypeScript 4.2.2
The text was updated successfully, but these errors were encountered: