[FR]: Copy tags improvement: Add the ability to copy dataview simple values to tags about obsidian-github-publisher HOT 13 CLOSED

Hmmm, after summarize this, finally i think it can be usefull throught Publisher.

Do you have the dataview function to get inline metadata ?

from obsidian-github-publisher.

Thanks you for this reply and bug issue ! I fixed it :) Could you please try the last update ? :)

Thanks for the quick fix! Works perfectly now.

from obsidian-github-publisher.

I think this suggestion is irrelevant for the plugin. It needs to handle too much parameters/regex. If you need to add tags to your note with using dataview, just edit it with using templater/quick add.

from obsidian-github-publisher.

I think this suggestion is irrelevant for the plugin. It needs to handle too much parameters/regex. If you need to add tags to your note with using dataview, just edit it with using templater/quick add.

Hmm, shouldn't it be easy enough to utilize dataview API to do this instead of relying on regex?

{
    ...
    "created": "2021-12-28 00:00",
    "updated": "2021-12-28 00:00",
    "title": "youtube-dl download subtitle only",
    "share": true,
    "website": "en/notes",
    "status": "#notes/archives",
    "knowledge": { // Link
        "path": "Linux.md",
        "type": "file",
        "embed": false
    }
}

from obsidian-github-publisher.

How can you notice that the knowledge is a link, tag, string, list... TBH i don't think it's useful/relevant in the purpose of the plugin?

from obsidian-github-publisher.

How can you notice that the knowledge is a link, tag, string, list... TBH i don't think it's useful/relevant in the purpose of the plugin?

Simply by checking typeof?

• link => use its text.
• string => use as is.
• tag => use without spaces or slashes.
• array => deal with each as previous.

The point of my suggestion is to improve reachability of content on platforms like Hugo by appending certain DV inline fields to tags, since inline fields are useless outside obsidian. So, it's kind of sub-feature of inline tags to tags feature.

Honestly, I think it's relevant to the plugin note content process part.

from obsidian-github-publisher.

But you could add the tags directly using templater ?

from obsidian-github-publisher.

But you could add the tags directly using templater ?

That's totally possible, but this approach will have some problems in my opinion:

• It will pollute tags for someone that heavily depends on dataview annotations for categorizing topics instead of tags.
• It works only well when I already know where does this note belong.
• The tag be always added to the note.

from obsidian-github-publisher.

For me, dataview is not designed to be published. I don't want to add theses option because it will polute more and more the settings, as I need to add :

• Textaera to get the field
• Add a way to exclude value
• Call dataview API to get the internal field
• Check every value of the choosen fields, as string, link, or array
• Get only the string part as an array, filter the list with excluded value
• Modify again the frontmatter with parseYaml and stringify.

This will add more and more options to just set tags based on dataview value...

from obsidian-github-publisher.

Hmmm, after summarize this, finally i think it can be usefull throught Publisher.

Do you have the dataview function to get inline metadata ?

No idea if there's such function to get only inline metadata, but I think there's no need to filter only inline, as the workflow can simply go like: values from users and access value directly using dataview.page("current page path")[key]

from obsidian-github-publisher.

I updated in beta (to try this time ;) the plugin ! Could you please try / beta test this function ? :)

from obsidian-github-publisher.

I updated in beta (to try this time ;) the plugin ! Could you please try / beta test this function ? :)

Awesome!

Just gave it a try, works well with single or multiple links values, but apparently it removes other tags copied by inline to tags feature by mistake?
Here's an example

from obsidian-github-publisher.

Thanks you for this reply and bug issue ! I fixed it :)
Could you please try the last update ? :)

from obsidian-github-publisher.