Open rx-chris opened 7 months ago
Automatic renaming is not really an option since tag pages can literally be named anything and placed anywhere in the vault. It might be reasonable to add extra text to the rename warnings to indicate how tag pages will be affected though, and suggest people make those changes prior to renaming the tags.
Well I do get it and the truth is, I also really like the flexibility of Tag Pages being able to be named anything and I believe that this should not change. That being said, I noticed that there is also a default naming convention that is currently used by Tag Wrangler when you create a new Tag Page using its context menu. I am following that default naming convention at the moment which is why I am suggesting an OPTIONAL setting that can be toggled on/off the Tag Wrangler settings:
Well, It might be a little ambitious at this point, considering Tag Wrangler does not yet implement any settings at the moment.
Personally, I plan to write a macro script using the QuickAdd API to rename my Tag Pages to match my renamed tags anyway but I thought it would makes sense to include this as a feature since Tag Wrangler is already implementing its own default naming convention for Tag Pages.
More than a little, yes. I think the most likely scenario here is that I add events to announce the renaming of tags, so that another plugin could handle this. TW already issues events for tag page creation, so a dedicated "tag page name manager" plugin or macro set could handle maintaining a naming convention for tag pages, or even merge tag pages when their tags merge.
I will look into adding more events when I work on TW again, as well as adding more info to the rename warning.
The current issue
Proposed Solution
#new-tag-name
, the corresponding tag pages can also be renamed accordingly to "new-tag-name.md" , "new-tag-name (1).md", "new-tag-name (2).md".