You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a task metadata field named "status" and some queries that filter for status != "blocked" or status = "blocked". The queries used to work fine. But I just updated the plugin yesterday to 0.5.38 yesterday and the queries stopped working. I haven't updated in a few months, so I'm not sure what version it stopped working. If I change the field name to anything else, the queries work fine. So, if I change the metadata to [foo::blocked] and then query for foo = "blocked", the query works.
Seems like DV might have something special going on with metadata named status?
DQL
task where status = "blocked"
Returns 0 results, even though there are tasks with [status::blocked]
JS
No response
Dataview Version
0.5.38
Obsidian Version
0.15.3
OS
MacOS
The text was updated successfully, but these errors were encountered:
You are correct. status is a new metadata field at the task level. It contains the character inside the checkbox. It was implemented as part of #812 I think.
What happened?
I have a task metadata field named "status" and some queries that filter for
status != "blocked"
orstatus = "blocked"
. The queries used to work fine. But I just updated the plugin yesterday to 0.5.38 yesterday and the queries stopped working. I haven't updated in a few months, so I'm not sure what version it stopped working. If I change the field name to anything else, the queries work fine. So, if I change the metadata to[foo::blocked]
and then query forfoo = "blocked"
, the query works.Seems like DV might have something special going on with metadata named
status
?DQL
Returns 0 results, even though there are tasks with [status::blocked]
JS
No response
Dataview Version
0.5.38
Obsidian Version
0.15.3
OS
MacOS
The text was updated successfully, but these errors were encountered: