[chore][setup]: misleading idf.py not found error (VSC-1761)

[ClSlaid]

The original error message posting /tools/idf.py not found, meanwhile the extension don't search this directory, which is misleading.

This PR corrects those messages.

---

BTW, I ought to find out why this extension cannot detect my esp-idf installed with this ArchLinux AUR repo. The repo installs esp-idf to /opt/esp-idf, surely there is ./tools/idf.py or ./tools/export.sh.

Even I was sure of the existence of /opt/esp-idf/tools/idf.py, the extension still keeps yelling /tools/idf.py not found. Which I don't reproduce on the master branch. So it's assumed to be fixed and I'll just update the error message here.

---

Feel free to edit this PR, busy working recently.

---

Description

Please include a summary of the change and which issue is fixed.

Fixes... I hate summaries, here is what Copilot concludes:

This pull request improves the handling and reporting of ESP-IDF path validation in the setup flow. The main changes focus on more accurate error messaging and streamlining file access checks.

Error Messaging Improvements:

• Updated error messages in both main.ts and store.ts to display the actual path checked for ESP-IDF validity, making it clearer to users which path is problematic. [1] [2]

File Access Check Logic:

• Refactored the logic in SetupPanel.ts to ensure the file access check only proceeds when a path is provided, and to consistently use the full path to tools/idf.py in responses. This prevents unnecessary checks and improves accuracy in reporting. [1] [2]

Code Formatting:

• Minor formatting adjustment to the error message construction in SetupPanel.ts for consistency.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Steps to test this pull request

Provide a list of steps to test changes in this PR and required output

1. Click on "Command"
2. Execute action.
3. Observe results.

• Expected behaviour:

• Expected output:

How has this been tested?

Just opened configure extension, select existing toolchains, and type in an incorrect ESP-IDF's path like /booger/aids to see if it reminds path /booger/aids/tools/idf.py not found.

Dependent components impacted by this PR:

None.

Checklist

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

[brianignacio5]

LGTM

[Copilot]

Pull Request Overview

This PR corrects misleading error messages in the ESP-IDF setup flow by updating error messages to display the actual path being checked for validation instead of a generic "/tools/idf.py" message.

• Updates error messages in setup store and main to show the specific path that failed validation
• Refactors file access check logic to ensure proper path handling and prevent unnecessary checks
• Improves accuracy in error reporting by displaying the full path to tools/idf.py in responses

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/views/setup/store.ts	Updates error message to display the actual path checked instead of hardcoded "/tools/idf.py"
src/views/setup/main.ts	Updates error message to use the specific path from the response message
src/setup/SetupPanel.ts	Refactors file access check logic and ensures consistent path reporting in responses

[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

[ClSlaid]

/cc @brianignacio5 merge it if you feel this PR is fine.

[brianignacio5]

LGTM

[Fabricio-ESP]

Thanks for the update.