-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: validate CLI installation and version during activation of CLI Integration extension #5185
Conversation
…if CLI is not installed
…is unsupported + cleanup code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :) Waiting on the tests for approval. Thanks Daphne! 🥳
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some feedback for your consideration
Co-authored-by: peternhale <[email protected]>
…tion.ts Co-authored-by: Cristina Cañizales <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All good from QA perspective both in mac and windows! ✅
After the text updates I'd say
Nice work Daphne! 🥳
QA doc here
Co-authored-by: peternhale <[email protected]>
The text for the message recommending the move to SF from SFDX is here. |
What does this PR do?
This PR includes new functionality to check whether a supported CLI version is installed on the user's computer. There are 4 main cases that are being caught: (1) CLI not installed (2) Outdated version of SFDX CLI that is incompatible with our extensions (3) Only SF v1 is installed (4) Both SFDX v7 and SF v2 are installed. In each of those 4 cases, the CLI Integration extension will not activate, and the user will not be able to see SFDX commands in the command palette. The user will receive an error notification about the unsupported/missing CLI when the activation of the CLI Integration extension fails.
What issues does this PR fix or reference?
@W-14196710@
Functionality Before
As a result of the recent switch from SFDX -> SF-style variables to get rid of warnings in the Output tab, users with a CLI version below SFDX v7.193.2 are no longer able to use the extensions because older CLI versions do not support SF-style variables. The extensions will activate, but the older version is caught at runtime.
Functionality After
If the user does not have CLI installed on their computer or their installed CLI version is no longer supported, they will get an error notification when they first create/open a Salesforce Project and the CLI Integration extension will not activate. Based on the case, one of these 4 error messages will pop up: