Bug Description
Hi!
I found a small inconsistency in the „convert current note to task“ command.
I have configured my TaskNote plugin to use „aliases“ as the Title field, which works for freshly created tasks. But when I use the command on an existing note that already has an aliases property set, then the task modal‘s title will be set to the basename of the file, not the already set title. And even worse: when I then create the task, it completely overwrites the aliases.
Maybe it is just not really supported to use a list property as the title field, but it does work in most other features of the plugin, so I figured to report this.
Also, in the original feature request it was defined that the command should inherit all already set properties — so at least this really is a bug.
Love the plugin, keep up the good work!
Steps to Reproduce
- Configure your plugin to use aliases as the title (see below)
- Create a note and set aliases to a list of strings with at least one entry that should be used as the task title
- Use the convert note to task command and confirm that the defined alias is not used as the task title but the filename
- Save the task and confirm that the old alias is now completely gone from the note
Versions
- Obsidian: 1.12.7 (303)
- TaskNotes 4.11.1
Affected Task Frontmatter
——
aliases:
- "My fancy Task Title"
—-
Relevant Settings or Customizations
data.json excerpt:
{"fieldMapping": {"title": "aliases"}}
Bug Description
Hi!
I found a small inconsistency in the „convert current note to task“ command.
I have configured my TaskNote plugin to use „aliases“ as the Title field, which works for freshly created tasks. But when I use the command on an existing note that already has an aliases property set, then the task modal‘s title will be set to the basename of the file, not the already set title. And even worse: when I then create the task, it completely overwrites the aliases.
Maybe it is just not really supported to use a list property as the title field, but it does work in most other features of the plugin, so I figured to report this.
Also, in the original feature request it was defined that the command should inherit all already set properties — so at least this really is a bug.
Love the plugin, keep up the good work!
Steps to Reproduce
Versions
Affected Task Frontmatter
Relevant Settings or Customizations
data.json excerpt:
{"fieldMapping": {"title": "aliases"}}