Contributed problemMatchers can't use Command variables

[elonmallin]

package.json contributes.problemMatchers can't use command variables like ${command:myextension.mycommand}.

Steps to Reproduce:

1. Create an extension with a problem matcher like:

"problemMatchers": [
      {
        "name": "myproblemmatcher",
        "owner": "php",
        "fileLocation": "relative",
        "pattern": [
          {
            "regexp": "^${command:myextension.mycommand}$"
          },
          {
            "regexp": "error: ${command:myextension.mycommand}(.*):(\\d+)",
            "file": 1,
            "line": 2
          }
        ]
     }
]

2. Use the problem matcher and notice this doesn't find problems.

What I'm trying to achieve is replace part of the file based in my myextension.mycommand command so that the relative file location becomes correct.
I'm aware this usually doesn't happen but this is a scenario where I'm running a command in a docker container and the path mapping then becomes completely wrong and I need to be able to replace part of the path dynamically.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Feature Request: Enable when clause to query complex configuration (#67745)

[alexr00]

It sounds like what you really want here is to contribute a problem matcher that reads the terminal output and does something with it instead of just a regex. Duplicate of #11663

[vscodebot]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

[elonmallin]

@alexr00 Well, not sure. I would be fine with just being able to use a command variable in my contributed problemMatchers regex.

I thought this was possible since problemMatchers are defined in tasks.json normally. And the docs say that command variables can be used in tasks.json.

So the bug would be that problemMatchers that are contributed can't use command variables but problemMatchers defined in tasks.json can I guess.

[elonmallin]

It's not only command variables that doesn't work in contributed problem matchers regex but also environment and config variables.

[alexr00]

I will update the documentation to make it clear that variable substitution is not supported in the problem matchers section of tasks.json. The way to make more complex problem matchers will be with the API changes required by #11663.