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
{{ message }}
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
It would be valuable for users to be able to distinguish between what I'll call "implicit" and "explicit" filtering of calls within the stack. To explain what I mean by this I will refer to a slightly modified example from the docs:
In this modified case we include an additional public_function which gets called by secret_function. Now if we want to filter out the secret, the fact that a call to eat leads to public_function is implicit (i.e. there is no line connecting their respective nodes):
What I propose is that there be an option to make the connection between eat and public_function "explicit" while still hiding secret_function. I came across a need for this functionality while trying to filter out the presence of a particularly widespread decorator from my call graph. However after having filtered out the decorator my graph became unreadable due to the fact that all call relationships that included it were removed completely (as I demonstrate above).
To overcome the issue of implicit filtering, we would want a graph that looked like this:
It would be valuable for users to be able to distinguish between what I'll call "implicit" and "explicit" filtering of calls within the stack. To explain what I mean by this I will refer to a slightly modified example from the docs:
In this modified case we include an additional
public_function
which gets called bysecret_function
. Now if we want to filter out the secret, the fact that a call toeat
leads topublic_function
is implicit (i.e. there is no line connecting their respective nodes):What I propose is that there be an option to make the connection between
eat
andpublic_function
"explicit" while still hidingsecret_function
. I came across a need for this functionality while trying to filter out the presence of a particularly widespread decorator from my call graph. However after having filtered out the decorator my graph became unreadable due to the fact that all call relationships that included it were removed completely (as I demonstrate above).To overcome the issue of implicit filtering, we would want a graph that looked like this:
To do so we can simply replace this line with:
I am unsure of whether this is truly the correct way to implement this feature though...
The text was updated successfully, but these errors were encountered: