Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Elaws opened this issue Nov 17, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Elaws
Copy link

Elaws commented Nov 17, 2024

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 : #621).

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

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 Elaws added the enhancement New feature or request label Nov 17, 2024
@Elaws Elaws changed the title [FEATURE REQUEST] Improving QuickAdd prompts compatibility using format syntax with the new Obsidian properties types (list, checkbox, date, date & time) ? [FEATURE REQUEST] Improving QuickAdd format syntax compatibility with the new Obsidian properties types (list, checkbox, date, date & time) ? Nov 17, 2024
@Elaws Elaws changed the title [FEATURE REQUEST] Improving QuickAdd format syntax compatibility with the new Obsidian properties types (list, checkbox, date, date & time) ? [FEATURE REQUEST] Improving QuickAdd format syntax compatibility with the new Obsidian properties types (list, checkbox, date, date & time, number) ? Nov 24, 2024
@userrand
Copy link

userrand commented Jan 1, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants