Skip to content
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

[BUG] : routing was not showing due to an exception error #364

Closed
kunjan343 opened this issue Nov 9, 2017 · 8 comments
Closed

[BUG] : routing was not showing due to an exception error #364

kunjan343 opened this issue Nov 9, 2017 · 8 comments

Comments

@kunjan343
Copy link

Overview of the issue

I changed route module as per described in live example to expose my routes in compodoc, document was also generated successfully. All pages working fine. except for routes. When I open routes menu It is throwing me an error.

image

-> Uncought TypeError: e.sort is not a function from d3.v3.min.js file

Operating System, Node.js, npm, compodoc version(s)

OS : ubuntu 14.04
NodeJs : v7.7.4
npm : v4.1.2
compodoc : v1.0.4

Compodoc installed globally or locally ?

locally as dev dependency

@kunjan343
Copy link
Author


Here is my route file

@kunjan343
Copy link
Author

Hey, I debug build code and found a bug, check the red box

@vogloblinsky
Copy link
Contributor

Ok related to #216

@kunjan343
Copy link
Author

And also the children is another route constant which is defined in separate file. So, we have to detect it to display on route.

@vogloblinsky
Copy link
Contributor

Yes, we have to detect it is a dynamic variable, find it in imports or misc variables. I have done the same thing for component/directive metadatas a5a3027

@kunjan343
Copy link
Author

I tested it by manually generating my tree data and now its working. The only thing we are missing is reading external routes from different file.

@vogloblinsky
Copy link
Contributor

Yes, i have added in milestone 1.0.5. stay tuned

@lock
Copy link

lock bot commented Sep 30, 2019

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.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants