Allow for more complex logic in templates

[steven-murray]

I'm trying to use this plugin with the TaskNotes plugin (https://tasknotes.dev/) which creates tasks as standalone obsidian notes with some specified YAML front matter.

Since this plugin saves each issue/PR as a Note, this almost works out of the box. I've made a custom template that adds the #task tag to each issue/PR note, which is the trigger that causes TaskNotes to treat it as a task.

However, TaskNotes also has a predefined set of labels for the status front-matter property that correspond to task states (todo, in-progress, done, etc). The github issues on the other hand have a status of open or closed.

It would be great to be able to do something like

{if {status}=='open': todo, elif {status}=='closed': done}

(I think this is poor syntax, but I hope you get the idea).

How possible do you think this would be?

[steven-murray]

This would also be useful for things like priority. On my Github issues I generally set these via labels (e.g. priority: low), and it would be nice to be able to detect this and set the priority property of my note.