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

[FEATURE] : migrate routes page to d3.js #17

Closed
vogloblinsky opened this issue Nov 14, 2016 · 4 comments
Closed

[FEATURE] : migrate routes page to d3.js #17

vogloblinsky opened this issue Nov 14, 2016 · 4 comments

Comments

@vogloblinsky
Copy link
Contributor

vogloblinsky commented Nov 14, 2016

@vogloblinsky vogloblinsky changed the title feat(app): migrate routes to d3.js feat(app): migrate routes page to d3.js Nov 14, 2016
@basarat
Copy link

basarat commented Jan 1, 2017

I've done stuff like this before e.g. using d3 to generate the AST https://basarat.gitbooks.io/alm/content/features/ast.html

In hindsight its better just done with html e.g. tree view https://basarat.gitbooks.io/alm/content/features/tree.html

Might even be able to use the component from here : https://astexplorer.net/

Ofcourse feel free to have as much fun as you want 🌹 ❤️ and thanks for making this OSS

@vogloblinsky
Copy link
Contributor Author

Thanks @basarat for your links.
The d3.js tree view seems to be the better option for me for displaying Angular routes.

Regarding all your amazing stuff with Typescript, i have a question for you.
I have implemented the source code view yesterday for compodoc:

source code view

I have tried to implement the 'GotoDeclaration' link for functions or properties of an Angular component or just a simple Typescript/ES6 class.
Typescript parser give us just 'pos' and 'end' information.
Did you have an idea for getting the line of the declaration with the 'start' information ?
I have started to code something with number of characters, etc, but didn't continue at all the stuff
Thanks.

@vogloblinsky vogloblinsky changed the title feat(app): migrate routes page to d3.js [FEATURE] : migrate routes page to d3.js Jan 3, 2017
@vogloblinsky vogloblinsky mentioned this issue Jan 4, 2017
4 tasks
@vogloblinsky
Copy link
Contributor Author

Current work with d3.js and tree view, support of guarded and lazy loaded routes
image

@lock
Copy link

lock bot commented Oct 1, 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 Oct 1, 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