[BUG][vscode-extension] Code Analyzer can't find SF CLI
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, vscode
Research direction
Start by reproducing the issue using the listed steps and compare VS Code launched normally with VS Code launched from a terminal. Investigate how the extension discovers the installed sf CLI, then verify that an installed CLI is found without the false missing-CLI error on the affected macOS setup.
Written by the indexing model from the issue text.
Description
Bug Description
We have had multiple reports of users who have the Salesforce CLI installed receiving an error message informing them they do not have the CLI installed, such as: "To use the Salesforce Code Analyzer extension, first install Salesforce CLI."
This can occur for a few reasons, but the root cause is that sf is not appearing in the PATH of the running VS Code instance. This tends to affect mac users when you have installed outside of the recommended CLI steps. We are currently looking into a fix for this.
Steps To Reproduce
- Open the Code Analyzer VS Code Extension
- See an error message that the CLI is not installed, preventing use.
Expected Behavior
If I have the SF CLI installed, Code Analyzer should be able to find it
Operating System
All
Visual Studio Code Version
Latest
Extension Version
1.10.1
Salesforce CLI Version
2.104.6
Code Analyzer CLI Plugin Version
5.4.0
Additional Context (Screenshots, Files, etc)
Workaround
Open VS Code using the terminal to ensure the sf is located in the path of your VS Code application. Re-install the CLI using the recommended steps. Do not use homebrew, or install SF with the assistance of sudo.
Urgency
Moderate
- Dominant language
- TypeScript
- Stars
- 240
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/code-analyzer
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
forcedotcom/code-analyzer#2094 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
forcedotcom/code-analyzer#2093 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
forcedotcom/code-analyzer#2091 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
forcedotcom/code-analyzer#2090 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
forcedotcom/code-analyzer#2101 ·
All issues in forcedotcom/code-analyzer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
diegosouzapw/OmniRoute#15401 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
code-yeongyu/oh-my-openagent#9454 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
smart-village-solutions/sva-studio#1654 ·
Maintainers usually reply within 1 day