Use case or problem
This is a great start to fixing some of the header/block reference updating issues. Don’t take this as a complaint but more of feedback for long term. I am curious if this is the “final” solution or just a temporary fix for now?
A couple of my problems / thoughts more long term:
Without knowing which headers are actually referenced somewhere else then I am left with “risking it” by changing a header more naturally/normal inline OR using the less natural right click each time I want to change any headers, which isn’t ideal.
You cannot use [[page ref]] autocomplete within the modal. I don’t expect you to be able to, but more just pointing out why using the right click menu isn’t ideal.
- For item 1, something helpful would be some sort of “indicator” that lets you know if a header is already referenced somewhere else. With block references you know because you will see the ^block-id at the end. For Headers you have no way of knowing whether one is already referenced somewhere else and therefore have to “guess” where you need to use the right-click to update or just more naturally update a header.
I posted this in insiders build discord channel as well.
In a perfect world you could just update a header reference naturally inline like you normally write and Obsidian would recognize those changes and update the links accordingly (automatically).
Another “solution” for me would be if you give a visual indicator of which Header lines are referenced somewhere else so that you know which headers you need to use the context menu update to make sure links update for it. Then you only have to worry about it for specific headers that are already referenced somewhere else.