quickadd icon indicating copy to clipboard operation
quickadd copied to clipboard

[FEATURE REQUEST] Improving QuickAdd format syntax compatibility with the new Obsidian properties types (list, checkbox, date, date & time, number) ?

Open Elaws opened this issue 1 year ago • 4 comments

Description

Currently, when using format syntax in our note templates for QuickAdd, there are no convenient ways to work with the new types of Obsidian properties.

Maybe this can be achieved with some QuickAdd javascript, but it would be very convenient to improve format syntax to achieve more fluency with the new Obsidian properties.

Proposed solutions

  • Property of type List :

image

It would be very useful to be able to add several values to properties of type List. Currently, it seems that [[Link1]], [[Link2]], etc... syntax is not supported by format syntax. (related FR : https://github.com/chhoumann/quickadd/issues/621).

It would be amazing that suggesters are reworked a little, it would make them much more convenient if they had :

  • An option for suggester so that we can select multiple entries that would be added to a List property.
  • An option to add a value that is not in the suggester (related FR : https://github.com/chhoumann/quickadd/issues/461)
  • An option to add a title to a suggester (related FR : https://github.com/chhoumann/quickadd/issues/202)

Related feature request :

  • Property of type checkbox :

image

To make a QuickAdd prompt compatible with a property of type Checkbox, a workaround could be to use {{VALUE:true, false}}, but as already mentioned above, it comes with the severe drawback of this prompt not having a title ! So we don't know which property we are modifying, like you can see here :

image

Another workaround could be to use {{FIELD:pro}} syntax, but you have to remember here that the only possible values are true or false for that property (if this is the first time that property is used, otherwise the values will be suggested).

image

  • Property of type date / date & time :

it would be very convenient to have a date or/and date & hour picker, like in the Obsidian properties.

image

image

Workaround : Use {{YYYY-MM-DDTHH:MM:SS}} or {{DATE}} format syntax in the template, so that it is compatible with Date & time or Date properties types (but it will input current date & hour, without possibility to pick a date directly in the QuickAdd prompt.

  • Property of type number

When entering properties of type number through the QuickAdd popup, they are entered in text format, leading to warning message :

image

Indeed, as you can see in source mode :

image


Many thanks for considering these improvements !

Elaws avatar Nov 17 '24 16:11 Elaws

It seem that clicking on the left side of the property in the template opens a menu and clicking the property type that one wants makes all of the files created using this plugin have the right property. When clicking the property type in the template, we do not see that the property type has changed as a ? icon continues to appear. On my laptop, Obsidian saved the property type even though I did not see a change in the template

userrand avatar Jan 01 '25 19:01 userrand

Hi @chhoumann , are there any plans concerning this FR ?

Thank you very much !

Elaws avatar Mar 05 '25 19:03 Elaws

Hey @Elaws, I certainly want to support this functionality. Only issue for me is finding the time to do it :)

chhoumann avatar Mar 08 '25 18:03 chhoumann

Thanks @chhoumann, I'm glad to know your interest for this FR, looking forward to hearing some news about it :)

Elaws avatar Mar 08 '25 18:03 Elaws

Hey! I've added partial support for all property types in 2.5.0. I'd appreciate any feedback!

Release notes: https://github.com/chhoumann/quickadd/releases/tag/2.5.0

chhoumann avatar Oct 10 '25 20:10 chhoumann

Hi @chhoumann so I've tested your latest update (2.6.0) but I'm unable to make it work in templates using format syntax :

  1. I tried with a "boolean" and a "number" type properties, with respectively {{VALUE:myBoolean}} and {{VALUE:myNumber}}, typed true and 42 there, but they get added as :
boolean: "true"
number: "42"

Which results in Type mismatch warning. I did enable "Format template variables as proper property types (Beta)" option.

  1. Can suggester prompts have a title ? It would be very useful. Because in case of a "true" or "false" choice ({{VALUE:true,false}}), how are we supposed to remember to what property does it correspond ?

  2. It would be useful for suggester to be able to select multiple values.

Thank you !

Elaws avatar Oct 20 '25 13:10 Elaws