Command Variable Substitution Failing

[ChrisBuilds]

It seems that command variable substitution is failing with the austin extension. When using a variable, the output contains the literal variable text rather than substituting the value. For example, here are two tasks, an Austin task, and a simple echo task to test substitution.

"tasks": [
{
    "label": "Austin Profile",
    "type": "austin",
    "file": "myscript/main.py",
    "args": [
        "${input:pickEffect}"
    ],
},
{
    "label": "echo",
    "type": "shell",
    "command": "echo ${input:pickEffect}"
}
],

When I run the 'echo' task, a prompt is provided to pick a string from the list provided in the pickEffect variable and the proper string is then echo'd.

However, when I run the Austin task, a prompt is provided to pick a string from the list provided in the pickEffect variable (as expected), but the text "${input:pickEffect}" is literally passed as an argument. No substitution is performed.

Running '/home/user/G/Programming/myscript/.venv/bin/austin' with args '-i 100 --pipe -s /home/user/G/Programming/myscript/.venv/bin/python /home/user/G/Programming/myscript/main.py ${input:pickEffect}'.
Profiling complete.

I have many command variables and they all work for other tasks and debugging, however none of them work with Austin. Is this an issue with the extension, or VSCode?

[P403n1x87]

@ChrisBuilds I believe variable substitution is not something that is done automatically by tasks, so it would have to be implemented in the extension. I will have to look into it, but of course contributions are very welcome 🙂