[Feature Request] Dev Tools Callback Graph - Allow hiding specific `DashDependency` objects

[petar-qb]

Related to the recent callback graph usability improvements, it would be extremely helpful to allow certain DashDependency objects to be completely excluded from the Dev Tools callback graph.

For example, being able to mark dependencies like the following as hidden:

Output("irrelevant_store", "data", hidden=True)

This would allow app authors to hide implementation details and internal wiring, keeping the callback graph focused on the dependencies that actually matter. For complex applications, this would significantly improve readability and reduce noise in the graph.

[antonymilne]

Just to be concrete, a couple of random examples for where this would be useful:

• you have a global setting (e.g. theme, language) that's used as input to all your callbacks
• you have a global status (e.g. callback in progress, callback completed) that's used as output of all your callbacks

In both these cases it could be nice to hide the global Dash dependency - otherwise you end up with many, many lines in the callback graph which you don't actually want to see. For the case of outputs one way around this is to use set_props, but that has other consequences, and for inputs you can't do it anyway.

[AnnMarieW]

Whatever happened to this initiative:

Pull Request: #2434
Forum discussion: https://community.plotly.com/t/callback-graph-improvements/72596

It seems like a much better solution to be able to search/sort/filter etc in the dev tools graph UI than messing with the app callbacks.

[antonymilne]

Oooh yes, that looks potentially very useful if it could be resurrected! The "Only display visible callbacks" option that @chriddyp mentions there would achieve #3586.