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
interface and claas that implements it ith same name
Expected Behavior
no crash
Actual Behavior
TypeDoc exiting with unexpected error:
RangeError: Maximum call stack size exceeded
at ProjectReflection.getReflectionById (C:\Repos\Claas\cde-fe-app\node_modules\typedoc\dist\lib\models\reflections\project.js:193:22)
at get reflection [as reflection] (C:\Repos\Claas\cde-fe-app\node_modules\typedoc\dist\lib\models\types.js:678:35)
at C:\Repos\Claas\cde-fe-app\node_modules\typedoc\dist\lib\output\themes\default\templates\hierarchy.js:17:30
at Array.map (<anonymous>)
at fullHierarchy (C:\Repos\Claas\cde-fe-app\node_modules\typedoc\dist\lib\output\themes\default\templates\hierarchy.js:16:33)
at C:\Repos\Claas\cde-fe-app\node_modules\typedoc\dist\lib\output\themes\default\templates\hierarchy.js:17:44
at Array.map (<anonymous>)
at fullHierarchy (C:\Repos\Claas\cde-fe-app\node_modules\typedoc\dist\lib\output\themes\default\templates\hierarchy.js:16:33)
at C:\Repos\Claas\cde-fe-app\node_modules\typedoc\dist\lib\output\themes\default\templates\hierarchy.js:17:44
at Array.map (<anonymous>)
The above example might look strange. Like this, the class Foo does not need to implement all the properties of interface Foo. The properties are just there (Mixin).
My assumption is, that this code leads to an endless loop.....or actually endless recursion of function function fullHierarchy(context, root)
Environment
Typedoc version: 0.25.7
TypeScript version: 5.1.6
Node.js version: 21.6.1
OS: Windows 11
The text was updated successfully, but these errors were encountered:
$ npx typedoc index.tsTypeDoc exiting with unexpected error:RangeError: Maximum call stack size exceeded at fullHierarchy (/home/me/fishProject/node_modules/typedoc/dist/lib/output/themes/default/templates/hierarchy.js:11:21) at /home/me/fishProject/node_modules/typedoc/dist/lib/output/themes/default/templates/hierarchy.js:17:44 at Array.map (<anonymous>) at fullHierarchy (/home/me/fishProject/node_modules/typedoc/dist/lib/output/themes/default/templates/hierarchy.js:16:33) at /home/me/fishProject/node_modules/typedoc/dist/lib/output/themes/default/templates/hierarchy.js:17:44 at Array.map (<anonymous>) at fullHierarchy (/home/me/fishProject/node_modules/typedoc/dist/lib/output/themes/default/templates/hierarchy.js:16:33) at /home/me/fishProject/node_modules/typedoc/dist/lib/output/themes/default/templates/hierarchy.js:17:44 at Array.map (<anonymous>) at fullHierarchy (/home/me/fishProject/node_modules/typedoc/dist/lib/output/themes/default/templates/hierarchy.js:16:33)
Unfortunately, I do not really know the purpose of such structures, but they exist (probably legacy code) and cause the issue mentioned above.
Search terms
Expected Behavior
no crash
Actual Behavior
Steps to reproduce the bug
The above example might look strange. Like this, the class
Foo
does not need to implement all the properties of interfaceFoo
. The properties are just there (Mixin).My assumption is, that this code leads to an endless loop.....or actually endless recursion of function
function fullHierarchy(context, root)
Environment
The text was updated successfully, but these errors were encountered: