Traverse currently shows all entrypoints in the generated call graphs and sequence diagrams, which creates large, overwhelming graphics that are difficult to analyze. When working with complex contracts like UniswapV2Pair that have dozens of public and external functions, the resulting diagrams become cluttered and nearly impossible to navigate. Developers trying to understand a specific execution flow get lost in the visual noise of unrelated function calls.
Traverse should allow users to filter and generate diagrams for one or more specific entrypoints like UniswapV2Pair.mint() or UniswapV2Pair.swap(). This targeted approach would make the output much more focused and readable, enabling developers to drill down into particular contract interactions without the distraction of irrelevant execution paths. Such filtering would be especially valuable for auditing specific functions or debugging particular transaction flows.
Traverse currently shows all entrypoints in the generated call graphs and sequence diagrams, which creates large, overwhelming graphics that are difficult to analyze. When working with complex contracts like UniswapV2Pair that have dozens of public and external functions, the resulting diagrams become cluttered and nearly impossible to navigate. Developers trying to understand a specific execution flow get lost in the visual noise of unrelated function calls.
Traverse should allow users to filter and generate diagrams for one or more specific entrypoints like UniswapV2Pair.mint() or UniswapV2Pair.swap(). This targeted approach would make the output much more focused and readable, enabling developers to drill down into particular contract interactions without the distraction of irrelevant execution paths. Such filtering would be especially valuable for auditing specific functions or debugging particular transaction flows.