Problem
Currently, the file.hasTags() function does not handle nested tags properly when filtering by tags in Properties using the Bases plugin.
For example:
If a note has the property:
tags: [project/english]
And the filter is set to file.hasTags(“project”), this note is not returned. This breaks the expected behavior of nested tag logic, where project/english should be treated as a child of project.
Why it matters
• The Dataview plugin already handles this correctly: filtering by #project includes notes with #project/english, #project/data, etc.
• Many users organize their notes hierarchically using nested tags in Properties, not inline.
• Current workaround using:
tags.toString().contains(“project”)
works, but cannot be used in the GUI filter and requires manual code editing, which is inconvenient and non-discoverable for most users.
Test Case
This YAML should match a project filter:
tags: [project/english]
But currently, it does not.
Expected Behavior
• When using file.hasTags(“project”), it should include any tag that starts with project/ as well.
• Nested tag matching should behave consistently between Properties and inline tags.
• Ideally, support this behavior in the GUI filter of Bases, not just in custom codeblocks.
Request
Please reconsider implementing proper nested tag support in Properties.
If not possible right now, please at least:
• Reopen the previous feature request/discussions
• Add this to a roadmap or known limitation list
• Provide a GUI-friendly workaround
Thank you for your amazing work! Bases is powerful — nested tag support would make it even more intuitive.
