You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey guys! I've been using Slither for some time now and found it quite useful, so thanks for all the effort you put into developing this tool.
While using the inheritance-graph printer, I found that the resulting graph contains several redundant inheritance lines that should be better left off the graph. For instance:
Note that there's a line that goes from Child to Grandparent which is redundant, as Child is already Parent and Parent is already Grandparent. While this example is pretty simple, in far more complex inheritance chains these extra lines add little to no value and the graph ends up being too cluttered with lines pointing everywhere.
I'm not sure if this is a feature you added on purpose or a bug. If the former, are you considering adding an extra flag to the printer so those extra lines are not included in the final inheritance graph?.
The text was updated successfully, but these errors were encountered:
Hey guys! I've been using Slither for some time now and found it quite useful, so thanks for all the effort you put into developing this tool.
While using the
inheritance-graph
printer, I found that the resulting graph contains several redundant inheritance lines that should be better left off the graph. For instance:Slither's printer output is:
Note that there's a line that goes from
Child
toGrandparent
which is redundant, asChild
is alreadyParent
andParent
is alreadyGrandparent
. While this example is pretty simple, in far more complex inheritance chains these extra lines add little to no value and the graph ends up being too cluttered with lines pointing everywhere.I'm not sure if this is a feature you added on purpose or a bug. If the former, are you considering adding an extra flag to the printer so those extra lines are not included in the final inheritance graph?.
The text was updated successfully, but these errors were encountered: