rioj7

@woung717 We can't define new variables to use in the launch config or task. We have to use the `${input:name}` and `${command:cmdID}` variables. An example is already in the readme:...

@woung717 A possible option would be to create a separate command for each variable: ```json "inputs": [ { "id": "def_vars", "type": "command", "command": "extension.commandvariable.defVariables", "args": { "world": "Hello, World!", "lorem":...

@woung717 if I define `extension.commandvariable.defVariable` as an alias of `extension.commandvariable.transform` you have the same config code. With your suggestion the key of the variable (`lorem`, `carpe`) is not immediately clear....

@woung717 You could use the `extension.commandvariable.remember` command to store a number of stuff to remember and return one of the keys. You have to do this in the first remember-input...

@KUGA2 You can store multiple keys when you pick an item. Just store the picked label string also. And use that as `description` in the `Use previous value` item. ```json...

@KUGA2 I removed 1 line from Version 1 `"rememberTransformed": true,`. I thought it is not needed here. ```json "key": "buildType1", "description": "What build type to use", "rememberTransformed": true, ```

@dvirtz the `update` method is async and I don't think I can call async stuff in the `deactivate` method of the extension. VSC has signaled that it is about to...

@dustinlacewell Can you show the task and its inputs, with anonymized names/text. Most likely you use a configuration I have not thought of.

@dustinlacewell Looking at the source code the only place I use `.apply` is in `variableReplaceAndFilter`. The only case where `replacement` is not a hard coded string literal or a function...

@LoggerMN Other users have also found this problem with launch configs. I have mentioned this in issue microsoft/vscode#215905 at the vscode repo in [comment](https://github.com/microsoft/vscode/issues/215905#issuecomment-2203948382) ---- I have found a workaround...