Add a new setting to preload all project tasks

[puzrin]

In 2.0.0 / 2.0.1

1. Terminal -> Run Build Task - no env-related items displayed (only single one with default target).
2. Terminal -> Run Task - the same.

I need a very simple thing - build/upload for selected hardware. Now this can be done only via explorer - too difficult to reach.

How to reproduce:

• Open https://github.com/speedcontrols/ac_sc_grinder
• Try Terminal -> Run Task / Run Build Task
• Go to extensions and force install 1.10.0, then compare content of menus.

[ivankravets]

Fetching ALL envs is expensive operation. PlatformIO IDE 2.0 now uses PlatformIO Core 5.0 that provide dynamics targets. See https://docs.platformio.org/en/latest/core/migration.html#custom-targets

We can't preload all targets from ALL envs by default. It does not make sense. Now, the developer personally decide which tasks to load. So, if you expand env tasks via PlatformIO: Tasks view - you will see them in Run Build Task.

Please note that you can drag PlatformIO: Tasks into the "Explorer" activity to avoid switching between activities.

[puzrin]

I don't agree with this approach:

• First, code is written for humans. It's not correct to argument with "feature dropped because implementaion become difficult".
• I do not need ALL possible targets preload into menu, only frequently used (build/upload, no custom)
• Your proposal about explored leafs expand could work, but:
  • PIO does not remember state after VSCode reload.
  • No way to define default state on first load.

---

Please, reconsider your decision. I have concrete use case: pre-populate Terminal menu with desired content (for me - 2 existing targets for each env). IMO such kind of use cases can be implemented somehow, with low CPU cost.

[ivankravets]

Thanks, I renamed this issue. We will add a new setting that will instruct PlatformIO to pre-load ALL tasks/targets.