Currently, the origins of the Reasons of nodes combined by a CombinedCallGraphNode are determined when the combined node is separated.
Sometimes the origin cannot be found and the combined NodeID is used instead.
This leads to very long results when the NodeID is stringified for the output json file.
Desired solution
Store the origin with the Symbol in the corresponding set of the Reasons object.
With this, every origin of each node in the CombinedCallGraphNodes can be determined.
Is your feature request related to a problem?
Currently, the origins of the
Reasons
of nodes combined by aCombinedCallGraphNode
are determined when the combined node is separated. Sometimes the origin cannot be found and the combinedNodeID
is used instead. This leads to very long results when theNodeID
is stringified for the output json file.Desired solution
Store the origin with the
Symbol
in the corresponding set of theReasons
object. With this, every origin of each node in theCombinedCallGraphNodes
can be determined.Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
No response