You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a type has a type argument and we use the default value for it, the type argument should not appear in the documentation.
Actual Behavior
Sometimes the type argument appears, sometimes it doesn't. It seems that Iterator<number> as a return type is rendered as Iterator<number> but as a parameter type is rendered as Iterator<number, any, undefined>.
Steps to reproduce the bug
I use Uint8Array for the repro because it is always present independent of the "lib" compiler option. Uint8Array just gained a type parameter in typescript 5.7 so this particular reproducer doesn't work in prior versions but it will reproduce with Iterator.
npm i typedoc@0.27 typescript@5.7
cat << 'END' > a.tsexport function f(a: Uint8Array): Uint8Array { return a;}END
npx typedoc a.ts
Output looks like:
Environment
Typedoc version: 0.27.5
TypeScript version: 5.7.1
Node.js version: 22.12
OS: ubuntu 22.04
The text was updated successfully, but these errors were encountered:
Expected Behavior
If a type has a type argument and we use the default value for it, the type argument should not appear in the documentation.
Actual Behavior
Sometimes the type argument appears, sometimes it doesn't. It seems that
Iterator<number>
as a return type is rendered asIterator<number>
but as a parameter type is rendered asIterator<number, any, undefined>
.Steps to reproduce the bug
I use
Uint8Array
for the repro because it is always present independent of the"lib"
compiler option.Uint8Array
just gained a type parameter in typescript 5.7 so this particular reproducer doesn't work in prior versions but it will reproduce withIterator
.Output looks like:
Environment
The text was updated successfully, but these errors were encountered: