Use case or problem
Preemptively you build a large complex vault with many navigational pretty links perhaps for a class. You consistently use many different variations of phrases for pretty links to many notes as you quickly build out vault.
Later, it comes time to use the vault, and because it was necessary for class to have a long ugly naming convention, you quickly realize that using pretty links going forward will pretty much be a must. Your notes look horrible in edit mode and you pat self on back and say, “you’ve made it this far without WYSIWYG”, and proceed knowing things are fine now (especially with potential of “Auto add pretty links to aliases” getting implemented in the perhaps nearer future for next “class”).
End daydream, and the harsh reality hits of the friction of building out aliases via searching the vault comes in. The other option is to manually build the pretty links as you go forward in this class, but you want to be consistent so you start devising a mass search and replace tactic but even doing that is painful and not perfect.
Proposed solution
A toggle that would allow you to enable auto adding all of a note’s different pretty link occurrences to a note’s alias list.
It is possible that more people might utilize and appreciate this feature if it had a per-note toggle. To be clear, the syncing would not be bidirectional. So adjusting an alias would not change all pretty links that used that alias. Also, more obviously but worth noting, you still have the ability to define aliases that never occur in vault in the form of a pretty link.
Final thought would be an option to have a dialog that asks if you want to add an alias after you create a pretty link. This dialog could have a “never ask me again option” controlling a toggle in settings. I would be pretty happy to see this as a plugin, but this feels like it isn’t too intrusive to be utilized via core plugin. I am under the impression that core plugins fall under umbrella of feature request. At least here on the forum where some newer users may be turned off when they hear plugin but don’t fully realize how Obsidian is a modular stack of core plugins, many enabled by default.
Sorry for the excessive length!
Thanks!
Relevant request/workaround: Add aliases to frontmatter by right click on a link with alias