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
Type checker in TypeScript playground ([see here]) can correctly deduce the type of SomeType to be any. I'm open to discussion about what TypeDoc should do in this situation, but I think that it at least should not crash.
Actual Behavior
TypeDoc fails to generate documentation due to the following error:
Error: Expected a symbol for node with kind FirstNode at C:/dev/typedoc-symbol-bug-repro/index.d.ts:5
at Context.expectSymbolAtLocation (C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\context.js:102:19)
at Object.convert (C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\types.js:374:37)
at Object.convertType (C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\types.js:76:30)
at Converter.convertType (C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\converter.js:60:24)
at Object.convertTypeAlias (C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\symbols.js:131:45)
at Object.convertSymbol (C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\symbols.js:80:79)
at Converter.convertExports (C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\converter.js:181:23)
at C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\converter.js:149:30
at Array.forEach (<anonymous>)
at Converter.compile (C:\dev\typedoc-symbol-bug-repro\node_modules\typedoc\dist\lib\converter\converter.js:147:17)
Search terms
node, symbol, property, any
Expected Behavior
It looks like in the following scenario
tsc
produces a node without a symbol forSource.SomeClass.someProp
([see AST viewer]):index.d.ts
Type checker in TypeScript playground ([see here]) can correctly deduce the type of
SomeType
to beany
. I'm open to discussion about what TypeDoc should do in this situation, but I think that it at least should not crash.Actual Behavior
TypeDoc fails to generate documentation due to the following error:
Steps to reproduce the bug
npm ci
npm run docs
Environment
The text was updated successfully, but these errors were encountered: