[feature request] scan the vault to find broken block ids and fix them all at once

[hyperphysin]

Coud you please add a function to scan the vault to find broken block ids and fix them all at once?

I'm scanning the vault with remove-unused-block-ids(https://github.com/isdmg/obsidian-remove-unused-block-ids) and then apply link-maintainer one by one, which is cumbersome.

[wenlzhang]

Thank you for your feature request! To better understand your needs, I have a few questions:

1. Can you describe your workflow of updating block links? Understanding how you use the plugin in your routine will help me understand the feature request better.
2. In what situations do you find yourself needing to replace invalid Block IDs in your entire vault? This insight will help me determine if this is a common scenario or more of a one-time task.
3. Regarding the Block IDs, just to clarify: Are the Block IDs themselves unchanged, and is it only the Block References that are becoming invalid? For example, when the text containing the block ID extracted into a new note, the block ID won't change but the block references become invalid?

[hyperphysin]

Thank you for your feature request! To better understand your needs, I have a few questions:

1. Can you describe your workflow of updating block links? Understanding how you use the plugin in your routine will help me understand the feature request better.

My current workflow is:

1. Scan vault with Remove Unused Block IDs plugin.
   
2. Click a block id in the search result to open the note cotaining it.
3. Use link maintainer to fix broken block references.
4. Repeat 2 and 3.
   Link maintainer made this workflow much easier and I appreciate it. And it'd be better if you could do this workflow with just one click! :)

2. In what situations do you find yourself needing to replace invalid Block IDs in your entire vault? This insight will help me determine if this is a common scenario or more of a one-time task.

Making invalid block references by refactoring a part of a note containing block ids happens unattended quite often to me.

3. Regarding the Block IDs, just to clarify: Are the Block IDs themselves unchanged, and is it only the Block References that are becoming invalid?

Yes.