Yes this would be good to have.

I think I see this as a duplicate of:

• Expose query.file.property similarly to task.file.property #3083

That other issue does require understanding ‘filter by function’ so is a little more advanced that the examples that you give.

But the example you give is rather more error prone in that not all users format their dates in the same way in YAML.

I apologize for not noticing this earlier.
I have reviewed the following documentation:
Obsidian Properties Limitations.

I look forward to the implementation of query.file.property() and hope it will support placeholders in the future.

Thank you for your time and effort.

Yes, that issue mentioned in the limitations is the same one I linked to above.

I can see how the connection was not obvious.

Once query.file.properties existed it would automatically be available in placeholders, although I would still worry about date formats.

Thank you for your response. I would also like to mention that Tasks has been incredibly helpful in both my personal and professional life. Since a similar issue has already been submitted, please feel free to close this issue.

Thank you for your response. I would also like to mention that Tasks has been incredibly helpful in both my personal and professional life.

You're very welcome - I'm glad it's been useful.

Since a similar issue has already been submitted, please feel free to close this issue.

Actually, it's proposing to implement a feature which is useful for those who do not know Javascript, so I've modified the title to show how it is different from #3083, and will keep it open.

Thank you for your response. I would also like to mention that Tasks has been incredibly helpful in both my personal and professional life.

You're very welcome - I'm glad it's been useful.

Since a similar issue has already been submitted, please feel free to close this issue.

Actually, it's proposing to implement a feature which is useful for those who do not know Javascript, so I've modified the title to show how it is different from #3083, and will keep it open.

Hi @claremacrae, is there any similar past issue/PR that I could have a look to, to figure out how the codebase works internally to purpose a PR with a consistent implementation?
Thank you!

Edit:
I already had a look at the contribution guide, I'd just like to have a reference to be consistent since it'd be a new introduction

Hi @NicolaCostantino - many thanks - I've spent half an hour so far going through my notes and finding-and-resurrecting my experiments from back in July... It's going to take a while longer...

Will post back either here in or in #3083 when I have something to report...

I have spent two hours on this, and need several more hours to give you something to start with, that does not need a lot of knowledge of the Tasks code....

Can you please give me an indication of what your timescales are, and how much time you might feasibly have to work on this?

@NicolaCostantino Moving the discussion to the lower-level issue...

• Expose query.file.property similarly to task.file.property #3083

This is also now implemented via these PRs.

• feat: partial support for query.file.property() and query.file.hasProperty() #3242
• fix: Allow multi-line properties in {{query.file.property('...')}} #3245

Those PRs describe the current limitations, and it needs documentation, but the basic facility is there now, and will be included in the next release - the date of which is not yet known.

I have just released this in Tasks 7.15.0.

The release notes have links to the relevant documentation pages.

I have just released this in Tasks 7.15.0.

The release notes have links to the relevant documentation pages.

The feature you created will be incredibly useful in my journal documents. Obsidian Tasks helps me easily see what’s more important and what’s more urgent. It makes my life simpler and clearer. I truly appreciate it. Thank you so much, Mrs. Macrae!