-
-
Notifications
You must be signed in to change notification settings - Fork 721
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
Use typescript 3.2.x #922
Use typescript 3.2.x #922
Conversation
There seems to be a type inference change with TypeScript 3.2 for the following statement const [destructArrayWithIgnoresA, , ...destructArrayWithIgnoresRest] = [1, 2, 3, 4]; With typescript 3.1, |
This should allow #881 to be merged as well |
So I'm not sure how to make TypeDoc aware of the new type inference for fixed-size array destructuring with I tried to follow the steps described in UPDATING.md, but on the
|
This reverts commit 8b63527.
I updated the destructuring specs to match what I would expect from TypeScript 3.2. Any pointers on how to meet these updated specs? I'd like to get the tests to pass. |
Try running the |
TypeStrong#922 https://github.com/Wenzil/typedoc commits: 476ed711fc804066514c0fd2886ef97e2df1869 8b63527 744514a 38bf09d
@Gerrit0 Could you share a bit more about what you learned around the tuple converter logic? |
@aciccarello I still don't really understand what's going on with tuples, I suspect there might be a bug where the Arrays are also weird, the tuple type check I came up with is basically the same as the array type check here: typedoc/src/lib/converter/types/array.ts Lines 19 to 27 in a2fab7c
I've opened ts-simple-ast#519 as David's library seems to have the same issue, and he might already know why this is happening. |
Thanks for your patience while figuring everything out! I clearly have more to learn about the type system. |
Allows generating documentation for projects requiring TypeScript 3.2