Inconsistent behaviour of "query.file.path" after a file rename when multiple opened files have a query using it

[William-A-A]

⚠️ Check issue is valid.

• My request is about the Tasks plugin for Obsidian.

⚠️ Check that this issue hasn't been reported before.

• I searched previous Tasks plugin Bug Reports didn't find any similar reports.

Steps to reproduce

1. Unzip the provided archive
2. Open the extracted folder as an obsidian vault
3. All files to reproduce are already opened in the vault
4. Instructions to reproduce are also in the vault, the key step here under
5. Verify taht File 1 and File 2 query are behaving as intended
6. Rename file 2
7. Swith to file 2 and confirm that File 2 query is not behaving as intended (query.file.path is mistakingly the recently renamed file 1).

queryfiletaskbug.zip

Expected Behavior

File 2 query correctly shows the tasks of File 2

Current behaviour

File 2 query show the tasks of "File 1" (after it is renamed)

Which Operating Systems are you using?

• Android
• iPhone/iPad
• Linux
• macOS
• Windows

Obsidian Version

1.8.9

Tasks Plugin Version

7.18.5

Checks

• I have tried it with all other plugins disabled and the error still occurs

Possible solution

SadlyI have no idea :(

[claremacrae]

Possibly related:

• {{query.file.property()}} picks up property of different file #3335

[claremacrae]

@William-A-A Is this really a minimal reproduction, in other words, did you try simplifying it...

Does the problem only occur when the file being renamed contains {{query.file.path}}?

[claremacrae]

Also to need to work out whether it only happens in Live Preview, Reading Mode or both.

[William-A-A]

Yes it's really minimal, new vault, only tasks plugin installed, only 3 files (1 with the instructions) simplest query I could make. with only the " path includes {{query.file.path}} "
It's reproduced in both Preview and Reading mode.
It clearly seems to be linked to the query.file.property issue, sorry I did not find it I searched for "path" and "renaming" in the bugs :(.

[William-A-A]

Oh also good catch .. The file beeing renamed doesn't need to include a query. I also reproduced "breaking" the query with the following actions :

• Renaming any other opened file
• Renaming any other file directly from the file tree
• Moving a non opened file from the file tree
• Moving an opened file with the command palette

[claremacrae]

Thanks for the extra info, really appreciated.

No worries about not spotting that other issue, I'm just able to spot related issues sometimes because I have to read every issue, and because I know the areas of code.

Also, this one will be a bit easier to debug than that other one, so this turned out to be helpful too. 😄

[William-A-A]

Maybe it can help : It weirdly remind me on how I had to do some changed to dataviewJs queries that would break when renaming or movig the file. instead of directly calling the dv.current I needed to query the active file using a function like this :

// Ensure always getting the latest active file state
function getCurrentPage() {
    const activeFile = app.workspace.getActiveFile();
    return dv.page(activeFile.path);
}

let currentPage = getCurrentPage();