Hi thanks for the suggestion. There seems to be a problem with the formatting of text which makes it hard to read.

Could you edit the description and fix it please?

Ah sorry about that, just fixed it. Thanks for the ping.

This feature would open up a bunch of opportunities to interact with other plugins too. Just as an example, one could define a button using meta-bind that modifies a property (to e.g. #personal #work) and could then have the task block update dynamically and show only work/personal tasks. One could build an entire task dashboard this way I guess 😁

I had the code for this when working on #2480 and it was buggy.

IIRC The biggest problem was that the query was not updated when I edited the frontmatter in the file containing the query, so I had to close and re-open the query file every time I edited its frontmatter.

So it was clearly not releasable, and I chose to release access to task.file.property as a first step, and document the limitation in https://publish.obsidian.md/tasks/Getting+Started/Obsidian+Properties#Limitations

I will edit that docs to reference this issue.

I will edit that docs to reference this issue.

Done:

Thanks for the explanation. Curious to see if there might be upstream improvements that fix this eventually.

Thanks for the explanation. Curious to see if there might be upstream improvements that fix this eventually.

No, it is code that needs to be written in Tasks. It is just competing with a lot of other requests, and finite development time.

Ah got it. Either way, just wanted to say again how much I appreciate all the work on this great plugin!

Plus 1 from me! 🙂 This would make templates so much more powerful, s you would just need to modify file properties to change the behaviour. By the way: The Tasks plugin is brilliant! 🤩

I think I really want this too.

My use case is that I have files representing people (who I need to do stuff for) or projects (that are big lists of related tasks) and when looking at either of those files, I want to be able to pick up related tasks by matching anything set as the current file tags.

Currently I've landed on:

tasks
not done
# searchTags needs to be manually updated until https://github.com/obsidian-tasks-group/obsidian-tasks/issues/3083
filter by function \
	const searchTags = ['#at-least-one-tag-here']; \
	const fileTags = task.file.property('tags'); \
	const allTags = task.tags.concat(fileTags); \
	return searchTags.find((tag) => allTags.includes(tag)) !== undefined;

but assuming I've fully understood the issue here, I'd like to just populate searchTags from query.file.property('tags') if this is implemented.

Edit: I too think the plugin is amazing!

Plus 1 from me!

@NicolaCostantino You kindly asked in #3154 (comment)

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

I have spent about 4 or 5 hours taking my initial experiments to the point where they have some tests and I understand the behaviour.

So here is the work for you have a look at:

main...query-accessing-properties

I've made an effort to describe in comments the issues that would currently stop me releasing the code as-is...

I actually have some free time this month to do a little pair-programming on Tasks, as my main pairer is unavailable until January, so if you wanted, we could have a Zoom call to talk through the code...

But first of all, could you drop some notes in here saying what you thing, and if you are indeed interested in picking this work up?
Many thanks.

@NicolaCostantino You kindly asked in #3154 (comment)

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

I have spent about 4 or 5 hours taking my initial experiments to the point where they have some tests and I understand the behaviour.

So here is the work for you have a look at:

main...query-accessing-properties

I've made an effort to describe in comments the issues that would currently stop me releasing the code as-is...

I actually have some free time this month to do a little pair-programming on Tasks, as my main pairer is unavailable until January, so if you wanted, we could have a Zoom call to talk through the code...

But first of all, could you drop some notes in here saying what you thing, and if you are indeed interested in picking this work up? Many thanks.

Hi @claremacrae,
thank you for this (I'll answer you directly here since I understood these two features could be somehow related to each other)

I'll have a look at the changes you referred to.

I could be more available this month as well to have a look at this and pairing would be great: I never worked on this codebase and Obsidian plugins before and I'm still figuring out the architecture, so any kind of onboarding would be more than appreciated!

I'd be deeply interested to have a look at this development since it's an actual blocker in my workflow and querying using dataview isn't a valid solution.

How should be proceed from there then?
I'm finishing having a deeper look at the doc and tracing the flow about your changes in the meanwhile, let me know what's next

Thank you!

Excellent!

How should be proceed from there then?

could you drop me an email - see my profile here for address… then we can set up a pairing session.

Ooooh - one more thought, @NicolaCostantino,

I'd be deeply interested to have a look at this development since it's an actual blocker in my workflow and querying using dataview isn't a valid solution.

Since you are so keen to use it out, you could stun two birds with one stone by:

1. Installing and using the code on the branch in to your vault - ideally by building it yourself (so you have a build already set up before we pair), or alternatively from downloading the dist....zip file in this build of the branch
2. Reading the code and tests on the branch, and the comments, you will be able to see what I have been able to implement so far - and then also the known limitations to be aware of.
3. Then you are definitely safe to use it in your own vault for real, to unblock your workflow!

In my experience, there's no substitute for trying out a feature on my own vault. If there are problems to be found I find them very quickly, when I know the data in the vault.

Your experience of this will be very helpful when we are considering if/when the feature will be ready for release....

That's a great insight @claremacrae , thank you!
I think I could set it up right tomorrow and then ping you right after via email.

That's great.

Not saying you would, but please don't spend more than an hour-or-so trying to set it up, if you have problems...

It would be better for us to set a date soon to meet, and get going, than for (maybe) days to pass before we even try to find a date to start working together... 😄

Hi @NicolaCostantino,

I've pushed some more fixes to the branch, and would really like to go ahead and set up at least our first pairing session ASAP...

It's better to talk than to wait, and with December holidays coming up fast, if we don't book something soon, we will have missed my window of opportunity.

So please could you email me when you have a moment...

Thanks in advance...

Hey @claremacrae,
I've sent you an email yesterday at the address on your profile
Thanks

This is 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.