Format Tags in YAML doesn't work as expected

[bmdesmet]

The rule "Format Tags in YAML" doesn't handle tags in the front matter formatted like

Tags:

• #foo
• #Bar

---

Applying the linter does nothing. The expected results were

Tags:

• foo
• Bar

---

My use case for this is that I find this style of lists in YAML to be more legible and easier to edit or remove a tag. I suspect the reason I start with the # is similar to others, we want auto-complete help when assigning tags.

[theopavlove]

The rule "Format Tags in YAML" doesn't handle tags in the front matter formatted like

Tags:

• #foo
• #Bar

Applying the linter does nothing. The expected results were

Tags:

• foo
• Bar

My use case for this is that I find this style of lists in YAML to be more legible and easier to edit or remove a tag. I suspect the reason I start with the # is similar to others, we want auto-complete help when assigning tags.

To be more precise, the following case does not work as expected:

---
tags:
- #tag1
- #tag2
---

The rule format-tags-in-yaml ignores the hashes as the original regex parses only a single string.

[neldeles]

A possible implementation for this is to have options on the desired output format after parsing out the #. Workflow would be:

1. Users type out their tags as suggested: tags: #tag1 #tag2
2. On save it's formatted based on the format output setting chosen by user i.e. bullet points, array

I myself prefer keeping my tags in an array e.g. tags: [ tag1, tag2 ] so a feature like this would be great.

[JeppeKlitgaard]

I also use this type of YAML list to do tags, and I think fixing this would be fantastic!

Ideally it would maintain the style used by the user, essentially just replacing the hashtags with nothing