prefer computed python venv path

[brianignacio5]

Description

Remove idf.pythonBinPath, idf.adapterTargetName, idf.customAdapterTargetName, idf.customExtraPaths, idf.selectedDfuDevicePath and idf.listDfuDevices in favor of calculating them from IDF_PATH and IDF_TOOLS_PATH.

Doctor command now computes ESP-IDF tools to be added in PATH and the used venv from IDF_PATH and IDF_TOOLS_PATH.

This should improve maintenance of extension, reduce setup issues and reduce regular docker file updates.

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Steps to test this pull request

This PR changes impact all the extension. It is necessary a full extension review for this PR to review avoid breaking existing features.

A basic test flow should include: Configure ESP-IDF extension, create project, build, flash monitor and debug as described in documentation.

Other features that requires ESP-IDF Tools or Virtual environment Python should also be review like: App Tracing, IDF Size UI and others. Doctor command now

• Expected behaviour: All extension features work the same as before but used settings are less than before.

• Expected output:

How has this been tested?

Ideally user should test this PR with all main features by following commands. A basic test flow should include: Configure ESP-IDF extension, create project, build, flash monitor and debug as described in documentation.

Test Configuration:

• ESP-IDF Version: 5.2
• OS (Windows,Linux and macOS): MacOS and Windows

Checklist

• PR Self Reviewed
• Applied Code formatting
• Added Documentation
• Added Unit Test
• Verified on all platforms - Windows,Linux and macOS

[github-actions]

Download the artifacts for this pull request:

• esp-idf-extension.vsix.zip
  Espressif docs preview

[radurentea]

Left some comments related to small changes in the documentation, other than that, LGTM!

[github-actions]

Pull request has been marked as stale since there are no activities, and this will be closed in 5 days if there are no further activities

[Fabricio-ESP]

Hi Brian,

There are 2 issues when installing this binary on windows machines.

1. When installing the extension using the VSIX binary on a clean VSCode I notice that the target device is not being set, whereas the current released extension will set it to default ESP32. (This is not a big deal as if you trigger the build it will set the default to ESP32)
   

2. When installing over a previous installation of the extension, the idf.pythonInstallPath setting is being set incorrectly:

• Installing on VSCode where the extension was previously installed:
  • "idf.pythonInstallPath": "C:\Users\FabricioRibeiro\.espressif\tools\idf-python\3.11.2\Scripts\python.exe"
• Installing on a clean VSCode:
• "idf.pythonInstallPath": "C:\Users\FabricioRibeiro\.espressif\tools\idf-python\3.11.2\python.exe"

This causes the extension to fail. Additionally restarting VSCOde will keep triggering the extension reconfiguration.

After running "Configure ESP-IDF Extension the setting was fixed to: "idf.pythonInstallPath": "C:\Users\FabricioRibeiro\.espressif\tools\idf-python\3.11.2\python.exe"

On Linux the binary worked as expected, no issues found.

[Fabricio-ESP]

Confirmed working on Windows and Linux for upgrading current installation and for new installation of the extension.