João Victor Tavares

@AshkanArabim Hey, you can use the `.callgraphignore` file to achieve what you want. You just need to ignore your Python path and maybe a virtual environment if you are using...

Hello! I've opened a PR with this suggestion #23 cc @beicause

@PrakashK94 Can you select "Show call hierarchy" on the function context menu and share the output? The output of this native VSCode API is used to draw the graphs. If...

@beicause Regarding "Make graph nicer." I'm exploring the idea of intercepting and editing the output svg to reflect the vscode theme colors. I had success intercepting and editing the SVG...

@beicause hey I have a PR with the change that adapts the graph colors to match the active vscode's theme #26

@jesseduffield Hello! I opened a PR to fix this issue. Please check out when you have time #633 . Thank you!

@AHJiapengZhang This extension relies on the [CallHierarchyIncomingCall](https://code.visualstudio.com/api/references/vscode-api#CallHierarchyIncomingCall) and [CallHierarchyOutgoingCall](https://code.visualstudio.com/api/references/vscode-api#CallHierarchyOutgoingCall) APIs. If implicit calls are not supported, then it's not going to show up in the graph. I reproduced your experiment...

@naiyouweibaomihua This extension relies on the [CallHierarchyIncomingCall](https://code.visualstudio.com/api/references/vscode-api#CallHierarchyIncomingCall) and [CallHierarchyOutgoingCall](https://code.visualstudio.com/api/references/vscode-api#CallHierarchyOutgoingCall) APIs. As long as the LSP you use for your preferred language implements the necessary bindings, it's gonna work for your...

Suggestion N.1

Suggestion N.2