[BUG] Route Page Exception
See original GitHub issueOverview of the issue
Generated Routes pages does not render any routes.
No error messages during generation.
Other pages working correctly.
Open Chrome Debugger, see the following:
prism.js:14 Uncaught TypeError: Cannot read property ‘toString’ of undefined at prism.js:14 at prism.js:14 (anonymous) @ prism.js:14 (anonymous) @ prism.js:14 d3.v3.min.js:2 Uncaught TypeError: e.sort is not a function at d3.v3.min.js:2 at ui (d3.v3.min.js:2) at n (d3.v3.min.js:2) at HTMLDocument.<anonymous> (routes.js:37)
Operating System, Node.js, npm, compodoc version(s)
Windows 10 Node 6.11.4 Compodoc 1.1.2
Angular configuration, a package.json
file in the root folder
Attached package.json.txt
Compodoc installed globally or locally ?
Globally installed compodoc
Motivation for or Use Case
We love compodoc, but desperately need to see the routing graph to
Reproduce the error
Routes_index.js as generated attached (plus pretty printed) routes_index.js.txt
Related issues
I see ‘similar’ issues, but have not been able to deduce the necessary changes (if it is our code). #216 ??
Suggest a Fix
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (2 by maintainers)
Top GitHub Comments
Ok reproduced. The children routes, for example
prototypeRoutes
are dynamic references Compodoc need to handles too to have a complete reference of all the routes during the parsing.This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.