Feature Request: variable holding the current env

[Jason2866]

which will allow users to use native VSCode's workbench.action.tasks.runTask and PlatformIO commands.

Example:

{
  "platformio-ide.toolbar": [
    {
      "text": "Clean Active Environment",
      "commands": [
        {
          "id": "workbench.action.tasks.runTask",
          "args": "PlatformIO: Clean (${command:platformio-ide.activeEnvironment})"
        }
      ]
    },
  ]
}

Reference #2623 (comment)

Thx @ivankravets

[ivankravets]

Fixed in 27e1411

Could you re-test with PlatformIO IDE 3.0.1-beta.3 for VSCode?

[Jason2866]

@ivankravets Nearly there :-)

Works perfect if env is selected via Platformio VSC IDE Options.

when used Default in Platformio VSC IDE

and the default_envs is set in platformio.ini it does not work as expected

The window opens to select an env

an not the set default_env is used.

[Jason2866]

Tested with

        "text": "$(refresh)",
        "tooltip": "Testing",
        "commands": [
          {
            "id": "platformio-ide.runPIOCoreCommand",
            "args": "pio run -t uploadfs -e ${command:platformio-ide.activeEnvironment}"
          }
        ]
      },

works fine with selection via Platformio VSC IDE.

Fails with set_default in platformio.ini since the ${command:platformio-ide.activeEnvironment} is not set (undefined).

Probably missing to set this entry:

[ivankravets]

Should be fixed in the pre-release version:

1. Navigate in VSCode to the Extensions activity bar
2. Click on the PlatformIO IDE
3. Switch to the PRE-RELEASE version.

Does it work now?

[Jason2866]

@ivankravets Great, it does work now! Thx for your awesome work and support :-)