[FEATURE REQUEST] Improving QuickAdd format syntax compatibility with the new Obsidian properties types (list, checkbox, date, date & time, number) ? #757
Labels
enhancement
New feature or request
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
List
: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 : #621).It would be amazing that suggesters are reworked a little, it would make them much more convenient if they had :
List
property.Related feature request :
checkbox
: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 :Another workaround could be to use
{{FIELD:pro}}
syntax, but you have to remember here that the only possible values aretrue
orfalse
for that property (if this is the first time that property is used, otherwise the values will be suggested).date
/date & time
:it would be very convenient to have a date or/and date & hour picker, like in the Obsidian properties.
Workaround : Use
{{YYYY-MM-DDTHH:MM:SS}}
or{{DATE}}
format syntax in the template, so that it is compatible withDate & time
orDate
properties types (but it will input current date & hour, without possibility to pick a date directly in the QuickAdd prompt.number
When entering properties of type
number
through the QuickAdd popup, they are entered intext
format, leading to warning message :Indeed, as you can see in source mode :
Many thanks for considering these improvements !
The text was updated successfully, but these errors were encountered: