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
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
Hey there,
It seems that import or called graph at a module (same for file) level are not available to date.
When I set up the view on one of my modules, I could see all its references on the right panel, which is already great for sure, but the equivalent graph view on the left panel is not available. "Only" the content of the module is displayed.
The closest I could get is if I go to the function level in my module, and there I could get the expected dependency graph, however I need to loop through all my functions and I could not get a clear overview of my module dependency.
Maybe this was intended as a design choice? having both the module contents and module called/import graph was too much information? Maybe this could be a toggled option.
Pushing it a bit further, It would be great if possible to do this module dependency for all the project actually (I admit that it's going to be quickly a mess maybe, but that would be really great to identify the critical modules, the cyclic calls,...)
Also, I wanted to precise that I just discover your tool (and I'm amazed !) so my apologies if I just miss the feature, but I couldn't found further info in the documentation.
Thanks !
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey there,
It seems that import or called graph at a module (same for file) level are not available to date.
When I set up the view on one of my modules, I could see all its references on the right panel, which is already great for sure, but the equivalent graph view on the left panel is not available. "Only" the content of the module is displayed.
The closest I could get is if I go to the function level in my module, and there I could get the expected dependency graph, however I need to loop through all my functions and I could not get a clear overview of my module dependency.
Maybe this was intended as a design choice? having both the module contents and module called/import graph was too much information? Maybe this could be a toggled option.
Pushing it a bit further, It would be great if possible to do this module dependency for all the project actually (I admit that it's going to be quickly a mess maybe, but that would be really great to identify the critical modules, the cyclic calls,...)
Also, I wanted to precise that I just discover your tool (and I'm amazed !) so my apologies if I just miss the feature, but I couldn't found further info in the documentation.
Thanks !
The text was updated successfully, but these errors were encountered: