Describe the bug
The output file analysis.json currently contains a key named system_dependency_graph which is a misnomer and does not accurately reflect the data it contains.
To Reproduce
Steps to reproduce the behavior:
- Run the analysis tool on any codebase
- Examine the resulting
analysis.json file
- Note that it contains both
system_dependency_graph and call_graph keys
Expected behavior
The analysis.json file should only contain the key call_graph since that accurately describes the data. The system_dependency_graph key should be removed as it's misleadingly named.
Additional context
The current naming creates confusion for users who expect the system_dependency_graph to represent something different than what it actually contains. This appears to be a legacy naming issue that should be resolved by standardizing on the more accurate call_graph terminology.
Describe the bug
The output file
analysis.jsoncurrently contains a key namedsystem_dependency_graphwhich is a misnomer and does not accurately reflect the data it contains.To Reproduce
Steps to reproduce the behavior:
analysis.jsonfilesystem_dependency_graphandcall_graphkeysExpected behavior
The
analysis.jsonfile should only contain the keycall_graphsince that accurately describes the data. Thesystem_dependency_graphkey should be removed as it's misleadingly named.Additional context
The current naming creates confusion for users who expect the
system_dependency_graphto represent something different than what it actually contains. This appears to be a legacy naming issue that should be resolved by standardizing on the more accuratecall_graphterminology.