Open blakeNaccarato opened 8 hours ago
Hi Blake,
Thanks for using Tasks.
With the exactly query you gave, I cannot reproduce the problem.
I recently updated Obsidian Tasks after few months of not updating
I maintain a special page for that situation:
https://publish.obsidian.md/tasks/What+is+New/Breaking+Changes
By coincidence, the feature that changed that behaviour celebrated its first birthday today!
The meaning of final backslash () characters on query lines
Reading that section of the docs will enable you to update your searches to get the original behaviour
PS I recommend adding the explain
instruction at the start of the query, whenever you have unexpected search results - or to verify your searches are doing what you expect.
Please check that this issue hasn't been reported before.
Steps to reproduce
I recently updated Obsidian Tasks after few months of not updating, and lots of my queries have started returning nearly every task in my vault. Queries which had a final
\
, e.g. in the "leaky" query below, would slow down Obsidian significantly and list all tasks in the vault. (The reason I often have trailing\
in queries is that I tend to mix/match query snippets and keeping the trailing\
is robust to changes in that query, e.g. moving that "clause" up or down, or elsewhere).I found that removing the
\
at the very end of the query restored functionality to what I expected from before updating, properly filtering tasks.I would say tentatively that this apparent "regression" has cropped up in one of the updates in the past ~six months. If there's an easy methodology for me to quickly "bisect" Tasks plugin versions to narrow down the exact release this happened on, or Obsidian Sync logs I'm unaware of, please let me know. My Sync history only shows in the manifest my recent update to 7.10.2, then updating to 7.11.1, so I can't exactly recall which version I updated from when this regression crept in.
Simple reproduction
one.md
andtwo.md
with the following contentstwo.md
. The only difference is the trailing slash. The leaky query "incorrectly" sees the task inone.md
.one.md
two.md
Correct query (no trailing slash)