[Feature Request] New Variable `{{tags}}`

[FelipeRearden]

This FR are being discussed here: #50

A new variable to manipulate tags from the active note based on the distinctive pattern.

[Taitava]

Done, will be released in 0.5.0.

Just one thing came to my mind: Each tag is prefixed with a #. If you don't want it, create another feature request about adding a second parameter (Something like {{tags:separator:no-hash}}) that would remove the # from tags.

[FelipeRearden]

Thank you very much @Taitava !!!!!!!!!!!!

If you don't want it, create another feature request about adding a second parameter (Something like {{tags:separator:no-hash}}) that would remove the # from tags.

Thanks for remembering this. I will see if a tag without hash is need and I let you know with a new FR !!

Thank you very much @Taitava !!! This new variable is going to help me a lot :)

[Taitava]

Implemented & released in 0.5.0.

[Taitava]

Each tag is prefixed with a #. If you don't want it, create another feature request about adding a second parameter (Something like {{tags:separator:no-hash}}) that would remove the # from tags.

If this is needed, it's now possible to do, as #43 is now done.

[FelipeRearden]

Hello @Tataiva!!!!!!!!!!!!

The :separator is fantastic and brings this variable to a level of customization that is amazing (more of this topic above)

I'd like to address 2 things for you:

1- Remove Duplicates Records (Distinctive)

In the example below, I have the tag grape repeating three times. When using this Shell Command, we have this

echo "{{tags:\n}}" | pbcopy

For tags I think would be a good idea to have one record of each tag as we talked in #50 :)

2- Tags inside YAML + :no-hash

Just one thing came to my mind: Each tag is prefixed with a #. If you don't want it, create another feature request about adding a second parameter (Something like {{tags:separator:no-hash}}) that would remove the # from tags.

Short conclusion: we need a no-hash separator to use all Obsidian Tags features.

Yesterday I was studying how Obsidian deals with tags. There are three ways to apply tags to a note

A- Inside the Note

The way we know without thinking too much ...

B- YAML: A List of Tags

tags:
- info01
- info02
- info03

Your approach is so clever that we can create this with the tag variable:

echo - "{{tags:\n- }}" | pbcopy

C- YAML: A Vector of Tags

tags: [info01,info02,info03]

Again, your approach is so clever that we can create this with the tag variable as well:

echo ["{{tags:,}}"] | pbcopy

---

After seen this, I'd to request, if possible, the no-hash separator. This way we close all the cases for tags variable in Obsidian :)

Sorry If I didn't get all of this in the first post of my FR. As a tester, this is my fault :(

As a user, I think the YAML approach is the best fit for me, because I can hide the yaml in the preview mode (since will be a huge list of tags from a book for example)

I will open a new FR as you said, but I just wanna explain before doing the FR :)

---

I really love this variable and what we can and will can do with :separator. It's groundbreaking

Thank you soo much for everything. You are super :)

[Taitava]

For tags I think would be a good idea to have one record of each tag as we talked in #50 :)

Damn, I forgot this duplicate test! Sorry! 🙁 My fault, not yours! 🙂 I count this as a bug and will reopen this issue, to handle this duplicate tags issue here.

I'll write about an idea regarding the no-hash thing in #62 .

I really love this variable and what we can and will can do with :separator. It's groundbreaking

Thank you soo much for everything. You are super :)

Thanks for the feedback! Good to hear that it (almost) works as intended! 🌞

[FelipeRearden]

Damn, I forgot this duplicate test! Sorry!

No problem at all. You have to deal with so many aspects of the feature that its normal :)

That's why I think that every user that open as FR have the responsibility to test the FR and give feedback to the developer.

• It's the least we can do to show our gratitude :)

Your #62 approach is AMAZING !!!!!!

Thanks again @Taitava !!!!

[Taitava]

Damn, I forgot this duplicate test! Sorry! 🙁 My fault, not yours! 🙂 I count this as a bug and will reopen this issue, to handle this duplicate tags issue here.

I'll actually create a new issue for this bug.

[FelipeRearden]

I'll actually create a new issue for this bug.

Ok @Taitava !!!!