My speculation why: if there's a lot of folders, then you'd have to use a lot of tags. That's a problem for 2 reasons:
Because in the graph there's no way to be selective about which tags are rendered, it's either all or nothing. Meaning to use this plugin in the scenario with a lot of folders, the graph becomes very "noisy" and #tags become less useful for their original purpose.
#tags are very finicky to deal with. For example lets say for whatever reason (tidying up / refactor vault) you want to delete a #tag from all notes. There's no easy way to do it. The best you can do is use tag wrangler and rename it to something else. However if you used a custom YAML field there is a way to bulk delete those fields from notes easily via the Linter plugin.
Someone has made a pull request enabling this capability (using custom YAML fields instead of tags) even if only at a rudimentary level:
What is going on?
For example, there has been numerous requests made to decouple this plugin from using
#tagsin Obsidian.My speculation why: if there's a lot of folders, then you'd have to use a lot of tags. That's a problem for 2 reasons:
Because in the graph there's no way to be selective about which tags are rendered, it's either all or nothing. Meaning to use this plugin in the scenario with a lot of folders, the graph becomes very "noisy" and
#tagsbecome less useful for their original purpose.#tagsare very finicky to deal with. For example lets say for whatever reason (tidying up / refactor vault) you want to delete a#tagfrom all notes. There's no easy way to do it. The best you can do is use tag wrangler and rename it to something else. However if you used a custom YAML field there is a way to bulk delete those fields from notes easily via the Linter plugin.Someone has made a pull request enabling this capability (using custom YAML fields instead of tags) even if only at a rudimentary level:
https://github.com/farux/obsidian-auto-note-mover/pull/53
It's been months since this PR (still not merged), and a full year since this repo was updated last...
What's up?