Types of changes

Changes visible to users:

• Bug fix (prefix: fix - non-breaking change which fixes an issue)

Internal changes:

• Tests (prefix: test - additions and improvements to unit tests and the smoke tests)

Description

This fixes one of the limitations from PR #3242 - the following now works:

Only single-line properties work. Multiple-line properties give an error message 'do not understand query'.

Note that continuation lines are not supported in multi-line properties, when they are used in placeholders.

Motivation and Context

Getting closer to releasing access to query.file.property() and query.file.hasProperty() to users...

See:

• Expose query.file.property similarly to task.file.property #3083
• Support for using YAML front Matter Values as Variables in Queries [via placeholder values, without the need for 'filter by function'] #3154

How has this been tested?

• Extra automated tests
• Exploratory testing

Screenshots (if appropriate)

Consider the following demo sample markdown note.

I have 3 Tasks searches, and they differ only in the happens date filter: I have a bunch of standard instructions that I want to use in all 3 searches.

Now, I can put all my standard instructions in a multi-line common_instructions property value, and embed its value as a placeholder in each of the 3 searches 🎉 :

---
common_instructions: |
  tags include #my/lovely/project
  short mode
  show tree
  show urgency
  group by due
---

- [ ] #task Do stuff - ==overdue== #my/lovely/project 📅 2024-12-21
- [ ] #task Do stuff - ==today== #my/lovely/project 📅 2024-12-22
- [ ] #task Do stuff - ==future== #my/lovely/project 📅 2024-12-23

## Overdue tasks

```tasks
{{query.file.property('common_instructions')}}
happens before today
```

## Tasks for today

```tasks
{{query.file.property('common_instructions')}}
happens today
```

## Future tasks

```tasks
{{query.file.property('common_instructions')}}
happens after today
```

Here are the search results:

Checklist

• My code follows the code style of this project and passes yarn run lint.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• My change has adequate Unit Test coverage.

Terms

• My contribution follows this project's contributing guide
• I agree to follow this project's Code of Conduct