[Bug]: Practical issues with applying filters to nested tasks: The `Expanded relationship` option does not work

[minol-dev]

Bug Description

In the latest version (4.5.0), the projects property now allows you to apply the Bases filter to nested tasks as well.

For example, consider the following tasks, where you want to view only Project A and its sub-tasks.

• project A
  • A-01
  • A-02

In older versions, simply adding note.projects.isEmpty() to the filter was sufficient.
However, in the current version, no subtasks are displayed due to the following reasons:

• project A ←note.projects.isEmpty()==true
  • A-01 ←note.projects.isEmpty()==false not displayed
  • A-02 ←note.projects.isEmpty()==false not displayed

However, if you remove the note.projects.isEmpty() filter, child tasks will be displayed at the same level as their parent tasks, making it impossible to manage them while maintaining the hierarchy. They will be displayed as shown below.

• project A
  • A-01
  • A-02
• A-01
• A-02

I tried changing the Expanded relationship option, but there was no change in the behavior described above.

Expected Behavior

I thought the Expanded relationship option determined whether the subtask filters inherited the Bases filters. Setting Expanded relationship to show-all would allow it to continue working with the older version's behavior.

Additionally, to resolve the issue described, it would be ideal to have an option to prevent child tasks from appearing at the top level when they are already displayed within their parent tasks.

Environment

Obsidian version: 1.12.7
TaskNotes plugin version: 4.5.0

[Glint-Eye]

Same here. The "Show All" setting doesn't seem to turn back on the old way of Subtask handling. I like that there is the Option for both, because both behaviours can be helpful for different use cases. Unfortunately right now, only the "Inherit" option seems to work.