[FR]: Better naming of the "Rename note" command

[stef-rausch]

Describe the solution you'd like

I was looking into how to refactor hierarchies with ST and "only" found the rename command.

How astonished was I, when I realised that this command does more than that. It renames all "deeper nested" levels too! Excellent, and it makes sense.

However, the naming of the command is not very clear outcome-wise. I suggest to rename it to "Refactor hierarchy" to emphasise what the renaming of a single note does, i.e., what positive "implications" it has.

If the user really wants to rename a single note without affecting the hierarchy -- the question is why -- then the user can use Obsidian's native commands.

👍

Additional context

N / A

[Rudtrack]

I've heard this feedback before, and I have considered it. However, I have been reluctant because if you're not a very "technical" person, then Refactor might not be that easy to understand. I'm always up for reconsidering though!

[stef-rausch]

Point taken. In your README you write:

• Structured Tree includes a built-in renaming modal for efficient note management. Renaming can be done by either using the command "Structured Tree: Rename note" or by right-clicking a note and selecting "Rename Note" from the context menu.

I suggest that you add something along the following lines:

• Notice: Note management in this context means that the renaming affects all children. Consider the following: If A is named book.awk.md and B book.awk.2nd-edition.md then renaming A to book.the-awk-programming-language.md will automatically rename B to book.the-awk-programming-language.2nd-edition.md to reflect the hierarchical naming scheme you are using. Happy refactoring!

Cheers.