While I very much like the idea of local graph, it cannot be a replacement for search and search indicator.
REAL LIFE USE CASE FOR SEARCH AND SEARCH INDICATOR ON LOCAL GRAPH
As an illustration, the following is one of my local graph in Obsidian. If one has to spot another node among this, it is still quite hard… Of course, I could increase the filter; a level 5 depth graph with all display criterion is a non-typical use case. But it is still useful, just a random look and the third level 5 node I found should be promoted to level 3.
Now I have the level 5 node in mind and want to observe the relationship with the central node (for that local graph) at a later time. I would need search and search indicator to reach it easily.
Let alone Anytype has note object which can contain single line text. There would be even more nodes and more relations. Another concept node might be 6-7 note node away from the central concept node.
ALTERNATIVE METHOD
I could definitely promote the level 5 node without delay, then I don’t need to come back it… but discovery observation and directed observation are two different processes for different purposes. People who maximise efficiency will separate these two working processes. And I would also want to observe the whole relationship pathway before executing the change for accurate amendment.
REMARKS
Local graph serves more functions. I suggest prioritising local graph ahead of this feature.
PS. I am already not a power user of Obsidian - only 460 existing files, but still this is already such a condensed local graph…
