ENV variables get updated only after condition evaluation

[funmaker]

Hello. I have bunch of files that I need to process in similar way. To accomplish that, I use extend and pass file name using env. Like this

[tasks.zip-all]
dependencies = ["zip-a", "zip-b"]

[tasks.zip-a]
extend = "zip"
env.ASSET_NAME = "a"

[tasks.zip-b]
extend = "zip"
env.ASSET_NAME = "b"

[tasks.zip]
command = "zip"
args = ["${ASSET_NAME}.zip", "${ASSET_NAME}.txt"]
condition = { files_modified = { input = ["${ASSET_NAME}.txt"], output = ["${ASSET_NAME}.zip"] } }

However, it seems that env.ASSET_NAME = "a" is evaluated after condition and propagates to the next task, which results in unexpected behavior:

$ ls
a.txt  a.zip  b.txt  Makefile.toml
$ makers zip-all
[cargo-make] INFO - makers 0.37.24
[cargo-make] INFO - 
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: zip-all
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Execute Command: "zip" "a.zip" "a.txt"
updating: a.txt (stored 0%)
[cargo-make] INFO - Skipping Task: zip-b 
[cargo-make] INFO - Build Done in 0.22 seconds.

Having to write similar looking condition to every file tedious very fast and is very prone to small but hard to detect mistakes. Is there any other way to make extended condition to depend on envvar or some other kind of variable?

[sagiegurari]

I'm not entirely sure what's the expectation is, but changing environment variables mutates the environment and therefore must be protected using the condition

[funmaker]

I would expect that ${ASSET_NAME} inside condition would resolve to the ASSET_NAME from the currently considered task, not from the previous one. So in the example it would skip zip-a and run zip-b.
If this is not how condition should work, then it would be nice to have some other way of declaring task templates with variables, so I could write similar tasks without having to repeat file names and stuff. Something like Ninja's rule statements.

[sagiegurari]

That's familiar with Ninja, but you can extend tasks meaning that you can define a template task and then extend it and just change the needed.
you don't have to rewrite everything all of the time

[funmaker]

Sure, but I have to write condition for every task because every task operates on different files. It would be nice if I could just declare eg input and output filename and extend from a task that has condition that will use these file names. Like in this example I included, it would be nice if ${ASSET_NAME} inside condition in the extended task would resolve to the ASSET_NAME from the currently considered task.

Otherwise every task has to look like:

[tasks.zip-b]
extend = "zip"
env.ASSET_NAME = "b"
condition = { files_modified = { input = ["b.txt"], output = ["b.zip"] } }

if I want condition to work. Which is really not that far from just explicitly writing all tasks without extending.