Global variables outside expressions like filter, sort, group, etc.

[hoangbn]

Is there a way I can assign "global" variables in a task query that I can then reuse inside each expression?

My main use case for this would be for caching: say I have some fairly costly function that uses query, and I want the result of it in an expression like filter. Right now, I could just make the calculation inside the filter expression, but this will be computed many, many times. I want to calculate it once outside, then reference it within the filter expression (or calculate it once for the first task inside the filter expression, but then reference it on subsequent tasks)

Another use case example, I want to define a global map variable that I can read and write to inside filter expression

[claremacrae]

No there is nothing built in.
Some people use the CustomJS plugin to have custom filter logic in one place - you can search this vault for CustomJs to find references to that.

But ca you give an example of a calculation that you feel is costly?

Normally the filter cost is negligible compared to task results rendering time.

[claremacrae]

But ca you give an example of a calculation that you feel is costly?

Closing as no reply....

[hoangbnc]

Oh sorry, I was trying out the custom JS plugin. Haven't had the chance to properly do it yet, but I think want I want to do is do-able through the plugin

[hoangbn]

Finally had the chance to take a look. The pattern you provided in #2392 (comment) works since we can compute things prior to constructing the tasksQuery. It can further be extended with CustomJS, as you mentioned. Thanks!

(My use case was quite similar the use case in that discussion, except I was looking to look for certain links recursively)

[claremacrae]

Thank you for the update.