Issue #241: Add Contract Dependency Graph Visualization#241
Merged
Timi16 merged 1 commit intoTimi16:mainfrom Feb 23, 2026
Merged
Conversation
Tijesunimi004
added a commit
to Tijesunimi004/soroban-debugger
that referenced
this pull request
Feb 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses Issue #241 by implementing the ability to analyze a contract's cross-contract call patterns and export a directed dependency graph. It supports visualizing the dependencies in both Graphviz (DOT) and Mermaid markdown formats natively from the CLI.
Key Changes
--dependency-graphflag in InspectArgs to accept a specified<FORMAT>mapping to a newly introducedGraphFormatEnum (Dot|Mermaid).flowchart TDstyling headers instead of the oldergraph LRformatting format.GraphFormat::DotorGraphFormat::Mermaid), ensuring unselected format strings are stripped and logs stay strictly isolated to the user-requested visualization format.Testing
cargo fmtto enforce codebase styling standards and executedcargo testverifying zero stability regressions across CLI integration mapping formats correctly.Related Issues
Closes #241