Releases: forcedotcom/salesforcedx-vscode
Release v55.4.1
55.4.1 - July 8, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted changes assoicated with PR #4240 due to issues with deploy/retrieve on windows.
55.4.0 - July 7, 2022
Fixed
salesforcedx-vscode-core
-
The links in the problems tab now correctly point to error locations in a file. (PR #4246, PR #4241)
-
Fixed an issue where making only a case change when renaming an Apex class caused an error. (PR #4240)
55.3.0 - June 29, 2022
Fixed
salesforcedx-vscode-core
- You can now access the
SFDX Create Apex Class
command when you right-click on a sub-folder of theclasses
project folder. (PR #4224)
55.2.0 - June 22, 2022
Fixed
docs
- We made some updates under the hood. (PR #4147)
salesforcedx-vscode-core
-
We fixed an issue where you could run the
SFDX Generate Manifest File
command to create a manifest file from any folder in your project. The command is now only available by right clicking on any folder or file in theforce-app
package directory folder. (PR #4208) -
We updated @salesforce/templates to 55.0.0 to give you a default unit test in addition to the other component files when you create a new LWC component using the template. (PR #4203)
55.0.0 - June 10, 2022
Added
salesforcedx-vscode-core
- Thanks to a contribution from @shunkosa, we updated our Japanese commands. We love our Open Source community. (PR #4186)
Fixed
salesforcedx-vscode-core
-
We made some updates under the hood. (PR #4165)
-
We fixed an issue where the
SFDX: Create Lightning Web Component Test
command threw an error when you exited out of the command prematurely. (PR #4143)
54.15.0 - June 1, 2022
Added
salesforcedx-vscode-core
- The SFDX: Rename Component command now prevents you from renaming an LWC or Aura component if the new name breaks any naming rules. New LWC component names are automatically revised to start with a lower-case letter if they don't already. (PR #4145)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- You can now use Ctrl+Space to retrigger autocomplete within code braces ({}) in an HTML file. Previously, if you moved away from or deleted content within code braces, you lost autocompletion. (PR #4144)
54.12.0 - May 14, 2022
Fixed
salesforcedx-vscode-core
- We added the ability to stop containerless function (PR #4025)
54.11.0 - May 4, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it prevents a component from being renamed if the component bundle already contains a file with that name. (PR #4039).
- Fixed some under-the-hood issues. (PR #4069).
54.9.0 - April 21, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it now correctly renames the file in the
__tests__
folder for LWC components that has the same name as the component being renamed (PR #4020). - We added support for debugging JavaScript in containerless functions (PR#4001).
- We fixed an issue that prevented
Standard Value Sets
from being displayed in the Org Browser(PR # 3992). Fixes Issue #1579
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of
.js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
- We now strip leading and trailing white spaces from the project name when you create a project using the
SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the ...
Release v55.4.0
55.4.0 - July 9, 2022
Fixed
salesforcedx-vscode-core
-
The links in the problems tab now correctly point to error locations in a file. (PR #4246, PR #4241)
-
Fixed an issue where making only a case change when renaming an Apex class caused an error. (PR #4240)
55.3.0 - June 29, 2022
Fixed
salesforcedx-vscode-core
- You can now access the
SFDX Create Apex Class
command when you right-click on a sub-folder of theclasses
project folder. (PR #4224)
55.2.0 - June 22, 2022
Fixed
docs
- We made some updates under the hood. (PR #4147)
salesforcedx-vscode-core
-
We fixed an issue where you could run the
SFDX Generate Manifest File
command to create a manifest file from any folder in your project. The command is now only available by right clicking on any folder or file in theforce-app
package directory folder. (PR #4208) -
We updated @salesforce/templates to 55.0.0 to give you a default unit test in addition to the other component files when you create a new LWC component using the template. (PR #4203)
55.0.0 - June 10, 2022
Added
salesforcedx-vscode-core
- Thanks to a contribution from @shunkosa, we updated our Japanese commands. We love our Open Source community. (PR #4186)
Fixed
salesforcedx-vscode-core
-
We made some updates under the hood. (PR #4165)
-
We fixed an issue where the
SFDX: Create Lightning Web Component Test
command threw an error when you exited out of the command prematurely. (PR #4143)
54.15.0 - June 1, 2022
Added
salesforcedx-vscode-core
- The SFDX: Rename Component command now prevents you from renaming an LWC or Aura component if the new name breaks any naming rules. New LWC component names are automatically revised to start with a lower-case letter if they don't already. (PR #4145)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- You can now use Ctrl+Space to retrigger autocomplete within code braces ({}) in an HTML file. Previously, if you moved away from or deleted content within code braces, you lost autocompletion. (PR #4144)
54.12.0 - May 14, 2022
Fixed
salesforcedx-vscode-core
- We added the ability to stop containerless function (PR #4025)
54.11.0 - May 4, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it prevents a component from being renamed if the component bundle already contains a file with that name. (PR #4039).
- Fixed some under-the-hood issues. (PR #4069).
54.9.0 - April 21, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it now correctly renames the file in the
__tests__
folder for LWC components that has the same name as the component being renamed (PR #4020). - We added support for debugging JavaScript in containerless functions (PR#4001).
- We fixed an issue that prevented
Standard Value Sets
from being displayed in the Org Browser(PR # 3992). Fixes Issue #1579
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of
.js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
- We now strip leading and trailing white spaces from the project name when you create a project using the
SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the new Start Function in Container command to run a Salesforce Function in a Docker container. The old command, Start Function now runs a function locally. ([PR #3838...
Release v55.3.0
55.3.0 - June 29, 2022
Fixed
salesforcedx-vscode-core
- You can now access the
SFDX Create Apex Class
command when you right-click on a sub-folder of theclasses
project folder. (PR #4224)
55.2.0 - June 22, 2022
Fixed
docs
- We made some updates under the hood. (PR #4147)
salesforcedx-vscode-core
-
We fixed an issue where you could run the
SFDX Generate Manifest File
command to create a manifest file from any folder in your project. The command is now only available by right clicking on any folder or file in theforce-app
package directory folder. (PR #4208) -
We updated @salesforce/templates to 55.0.0 to give you a default unit test in addition to the other component files when you create a new LWC component using the template. (PR #4203)
55.0.0 - June 10, 2022
Added
salesforcedx-vscode-core
- Thanks to a contribution from @shunkosa, we updated our Japanese commands. We love our Open Source community. (PR #4186)
Fixed
salesforcedx-vscode-core
-
We made some updates under the hood. (PR #4165)
-
We fixed an issue where the
SFDX: Create Lightning Web Component Test
command threw an error when you exited out of the command prematurely. (PR #4143)
54.15.0 - June 1, 2022
Added
salesforcedx-vscode-core
- The SFDX: Rename Component command now prevents you from renaming an LWC or Aura component if the new name breaks any naming rules. New LWC component names are automatically revised to start with a lower-case letter if they don't already. (PR #4145)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- You can now use Ctrl+Space to retrigger autocomplete within code braces ({}) in an HTML file. Previously, if you moved away from or deleted content within code braces, you lost autocompletion. (PR #4144)
54.12.0 - May 14, 2022
Fixed
salesforcedx-vscode-core
- We added the ability to stop containerless function (PR #4025)
54.11.0 - May 4, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it prevents a component from being renamed if the component bundle already contains a file with that name. (PR #4039).
- Fixed some under-the-hood issues. (PR #4069).
54.9.0 - April 21, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it now correctly renames the file in the
__tests__
folder for LWC components that has the same name as the component being renamed (PR #4020). - We added support for debugging JavaScript in containerless functions (PR#4001).
- We fixed an issue that prevented
Standard Value Sets
from being displayed in the Org Browser(PR # 3992). Fixes Issue #1579
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of
.js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
- We now strip leading and trailing white spaces from the project name when you create a project using the
SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the new Start Function in Container command to run a Salesforce Function in a Docker container. The old command, Start Function now runs a function locally. (PR #3838, PR #3856)
Fixed
salesforcedx-vscode
- We resolved the issue with the Diff Folder Against Org command being visible from the command palette even when an SFDX project wasn’t open. (PR #3843).
salesforcedx-vscode-apex
- We removed some unessential Apex classes from the A...
Release v55.2.0
55.2.0 - June 22, 2022
Fixed
docs
- We made some updates under the hood. (PR #4147)
salesforcedx-vscode-core
-
We fixed an issue where you could run the
SFDX Generate Manifest File
command to create a manifest file from any folder in your project. The command is now only available by right clicking on any folder or file in theforce-app
package directory folder. (PR #4208) -
We updated @salesforce/templates to 55.0.0 to give you a default unit test in addition to the other component files when you create a new LWC component using the template. (PR #4203)
55.0.0 - June 10, 2022
Added
salesforcedx-vscode-core
- Thanks to a contribution from @shunkosa, we updated our Japanese commands. We love our Open Source community. (PR #4186)
Fixed
salesforcedx-vscode-core
-
We made some updates under the hood. (PR #4165)
-
We fixed an issue where the
SFDX: Create Lightning Web Component Test
command threw an error when you exited out of the command prematurely. (PR #4143)
54.15.0 - June 1, 2022
Added
salesforcedx-vscode-core
- The SFDX: Rename Component command now prevents you from renaming an LWC or Aura component if the new name breaks any naming rules. New LWC component names are automatically revised to start with a lower-case letter if they don't already. (PR #4145)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- You can now use Ctrl+Space to retrigger autocomplete within code braces ({}) in an HTML file. Previously, if you moved away from or deleted content within code braces, you lost autocompletion. (PR #4144)
54.12.0 - May 14, 2022
Fixed
salesforcedx-vscode-core
- We added the ability to stop containerless function (PR #4025)
54.11.0 - May 4, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it prevents a component from being renamed if the component bundle already contains a file with that name. (PR #4039).
- Fixed some under-the-hood issues. (PR #4069).
54.9.0 - April 21, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it now correctly renames the file in the
__tests__
folder for LWC components that has the same name as the component being renamed (PR #4020). - We added support for debugging JavaScript in containerless functions (PR#4001).
- We fixed an issue that prevented
Standard Value Sets
from being displayed in the Org Browser(PR # 3992). Fixes Issue #1579
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of
.js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
- We now strip leading and trailing white spaces from the project name when you create a project using the
SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the new Start Function in Container command to run a Salesforce Function in a Docker container. The old command, Start Function now runs a function locally. (PR #3838, PR #3856)
Fixed
salesforcedx-vscode
- We resolved the issue with the Diff Folder Against Org command being visible from the command palette even when an SFDX project wasn’t open. (PR #3843).
salesforcedx-vscode-apex
- We removed some unessential Apex classes from the Apex LSP .jar file. (PR #3844)
54.0.0 - February 15, 2022
Added
salesforcedx-vscode
- Run the updated Launch Apex Replay Debugger with Current File to launch the Apex Replay Debugger from an A...
Release v55.0.0
55.0.0 - June 10, 2022
Added
salesforcedx-vscode-core
- Thanks to a contribution from @shunkosa, we updated our Japanese commands. We love our Open Source community. (PR #4186)
Fixed
salesforcedx-vscode-core
-
We made some updates under the hood. (PR #4165)
-
We fixed an issue where the
SFDX: Create Lightning Web Component Test
command threw an error when you exited out of the command prematurely. (PR #4143)
54.15.0 - June 1, 2022
Added
salesforcedx-vscode-core
- The SFDX: Rename Component command now prevents you from renaming an LWC or Aura component if the new name breaks any naming rules. New LWC component names are automatically revised to start with a lower-case letter if they don't already. (PR #4145)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- You can now use Ctrl+Space to retrigger autocomplete within code braces ({}) in an HTML file. Previously, if you moved away from or deleted content within code braces, you lost autocompletion. (PR #4144)
54.12.0 - May 14, 2022
Fixed
salesforcedx-vscode-core
- We added the ability to stop containerless function (PR #4025)
54.11.0 - May 4, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it prevents a component from being renamed if the component bundle already contains a file with that name. (PR #4039).
- Fixed some under-the-hood issues. (PR #4069).
54.9.0 - April 21, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it now correctly renames the file in the
__tests__
folder for LWC components that has the same name as the component being renamed (PR #4020). - We added support for debugging JavaScript in containerless functions (PR#4001).
- We fixed an issue that prevented
Standard Value Sets
from being displayed in the Org Browser(PR # 3992). Fixes Issue #1579
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of
.js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
- We now strip leading and trailing white spaces from the project name when you create a project using the
SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the new Start Function in Container command to run a Salesforce Function in a Docker container. The old command, Start Function now runs a function locally. (PR #3838, PR #3856)
Fixed
salesforcedx-vscode
- We resolved the issue with the Diff Folder Against Org command being visible from the command palette even when an SFDX project wasn’t open. (PR #3843).
salesforcedx-vscode-apex
- We removed some unessential Apex classes from the Apex LSP .jar file. (PR #3844)
54.0.0 - February 15, 2022
Added
salesforcedx-vscode
- Run the updated Launch Apex Replay Debugger with Current File to launch the Apex Replay Debugger from an Apex test file, an Anonymous Apex file, or an Apex log file. Previously, you could launch the Apex Replay Debugger only from an Apex log file. Also, we’ve simplified both the setup and execution of the command. You’re no longer required to create a launch configuration (launch.json) to run the Apex Replay Debugger, and you can debug your code with fewer steps. (PR #3779, PR #3827).
Fixed
salesforcedx-vscode
- The Generate Manifest File doesn’t show up as an option when you right-click on components within metadata types. Previously, the command showed up incorrectly even though it wasn’t executable ([PR #3818](https://github.com/force...
54.15.0 - June 1, 2022
Added
salesforcedx-vscode-core
- The SFDX: Rename Component command now prevents you from renaming an LWC or Aura component if the new name breaks any naming rules. New LWC component names are automatically revised to start with a lower-case letter if they don't already. (PR #4145)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- You can now use Ctrl+Space to retrigger autocomplete within code braces ({}) in an HTML file. Previously, if you moved away from or deleted content within code braces, you lost autocompletion. (PR #4144)
Release v54.12.0
54.12.0 - May 14, 2022
Fixed
salesforcedx-vscode-core
- We added the ability to stop containerless function (PR #4025)
54.11.0 - May 4, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it prevents a component from being renamed if the component bundle already contains a file with that name. (PR #4039).
- Fixed some under-the-hood issues. (PR #4069).
54.9.0 - April 21, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it now correctly renames the file in the
__tests__
folder for LWC components that has the same name as the component being renamed (PR #4020). - We added support for debugging JavaScript in containerless functions (PR#4001).
- We fixed an issue that prevented
Standard Value Sets
from being displayed in the Org Browser(PR # 3992). Fixes Issue #1579
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of
.js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
- We now strip leading and trailing white spaces from the project name when you create a project using the
SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the new Start Function in Container command to run a Salesforce Function in a Docker container. The old command, Start Function now runs a function locally. (PR #3838, PR #3856)
Fixed
salesforcedx-vscode
- We resolved the issue with the Diff Folder Against Org command being visible from the command palette even when an SFDX project wasn’t open. (PR #3843).
salesforcedx-vscode-apex
- We removed some unessential Apex classes from the Apex LSP .jar file. (PR #3844)
54.0.0 - February 15, 2022
Added
salesforcedx-vscode
- Run the updated Launch Apex Replay Debugger with Current File to launch the Apex Replay Debugger from an Apex test file, an Anonymous Apex file, or an Apex log file. Previously, you could launch the Apex Replay Debugger only from an Apex log file. Also, we’ve simplified both the setup and execution of the command. You’re no longer required to create a launch configuration (launch.json) to run the Apex Replay Debugger, and you can debug your code with fewer steps. (PR #3779, PR #3827).
Fixed
salesforcedx-vscode
-
The Generate Manifest File doesn’t show up as an option when you right-click on components within metadata types. Previously, the command showed up incorrectly even though it wasn’t executable (PR #3818).
-
The Execute Anonymous Apex code lens is now working as expected (PR #3819).
-
We fixed a broken video link in documentation (PR #3817).
53.16.0 - February 2, 2022
Added
salesforcedx-vscode-core
- The new Manifest Builder feature has been added to automatically generate a manifest file for a given set of metadata components instead of editing the package.xml file manually (PR #3784)
docs
- Updated development-models.md with a new section on Manifest Builder (PR #3788)
53.14.1 - January 19, 2022
Fixed
salesforcedx-vscode-apex-replay-debugger
- Backend changes to set up Anonymous Apex in replay debugging ([PR #3758](https://gi...
Release v54.11.0
54.11.0 - May 4, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it prevents a component from being renamed if the component bundle already contains a file with that name. (PR #4039).
- Fixed some under-the-hood issues. (PR #4069).
54.9.0 - April 21, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it now correctly renames the file in the
__tests__
folder for LWC components that has the same name as the component being renamed (PR #4020). - We added support for debugging JavaScript in containerless functions (PR#4001).
- We fixed an issue that prevented
Standard Value Sets
from being displayed in the Org Browser(PR # 3992). Fixes Issue #1579
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of
.js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
- We now strip leading and trailing white spaces from the project name when you create a project using the
SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the new Start Function in Container command to run a Salesforce Function in a Docker container. The old command, Start Function now runs a function locally. (PR #3838, PR #3856)
Fixed
salesforcedx-vscode
- We resolved the issue with the Diff Folder Against Org command being visible from the command palette even when an SFDX project wasn’t open. (PR #3843).
salesforcedx-vscode-apex
- We removed some unessential Apex classes from the Apex LSP .jar file. (PR #3844)
54.0.0 - February 15, 2022
Added
salesforcedx-vscode
- Run the updated Launch Apex Replay Debugger with Current File to launch the Apex Replay Debugger from an Apex test file, an Anonymous Apex file, or an Apex log file. Previously, you could launch the Apex Replay Debugger only from an Apex log file. Also, we’ve simplified both the setup and execution of the command. You’re no longer required to create a launch configuration (launch.json) to run the Apex Replay Debugger, and you can debug your code with fewer steps. (PR #3779, PR #3827).
Fixed
salesforcedx-vscode
-
The Generate Manifest File doesn’t show up as an option when you right-click on components within metadata types. Previously, the command showed up incorrectly even though it wasn’t executable (PR #3818).
-
The Execute Anonymous Apex code lens is now working as expected (PR #3819).
-
We fixed a broken video link in documentation (PR #3817).
53.16.0 - February 2, 2022
Added
salesforcedx-vscode-core
- The new Manifest Builder feature has been added to automatically generate a manifest file for a given set of metadata components instead of editing the package.xml file manually (PR #3784)
docs
- Updated development-models.md with a new section on Manifest Builder (PR #3788)
53.14.1 - January 19, 2022
Fixed
salesforcedx-vscode-apex-replay-debugger
- Backend changes to set up Anonymous Apex in replay debugging (PR #3758)
53.13.0 - January 13, 2022
Added
salesforcedx-vscode-apex
- Identify test class from uri (PR #3751)
Fixed
docs
- Updates to reflect runtime restrictions (PR #3741)
salesforcedx-vscode-apex
-...
Release v54.9.0
54.9.0 - April 21, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Rename Component command so that it now correctly renames the file in the
__tests__
folder for LWC components that has the same name as the component being renamed (PR #4020). - We added support for debugging JavaScript in containerless functions (PR#4001).
- We fixed an issue that prevented
Standard Value Sets
from being displayed in the Org Browser(PR # 3992). Fixes Issue #1579
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of
.js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
- We now strip leading and trailing white spaces from the project name when you create a project using the
SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the new Start Function in Container command to run a Salesforce Function in a Docker container. The old command, Start Function now runs a function locally. (PR #3838, PR #3856)
Fixed
salesforcedx-vscode
- We resolved the issue with the Diff Folder Against Org command being visible from the command palette even when an SFDX project wasn’t open. (PR #3843).
salesforcedx-vscode-apex
- We removed some unessential Apex classes from the Apex LSP .jar file. (PR #3844)
54.0.0 - February 15, 2022
Added
salesforcedx-vscode
- Run the updated Launch Apex Replay Debugger with Current File to launch the Apex Replay Debugger from an Apex test file, an Anonymous Apex file, or an Apex log file. Previously, you could launch the Apex Replay Debugger only from an Apex log file. Also, we’ve simplified both the setup and execution of the command. You’re no longer required to create a launch configuration (launch.json) to run the Apex Replay Debugger, and you can debug your code with fewer steps. (PR #3779, PR #3827).
Fixed
salesforcedx-vscode
-
The Generate Manifest File doesn’t show up as an option when you right-click on components within metadata types. Previously, the command showed up incorrectly even though it wasn’t executable (PR #3818).
-
The Execute Anonymous Apex code lens is now working as expected (PR #3819).
-
We fixed a broken video link in documentation (PR #3817).
53.16.0 - February 2, 2022
Added
salesforcedx-vscode-core
- The new Manifest Builder feature has been added to automatically generate a manifest file for a given set of metadata components instead of editing the package.xml file manually (PR #3784)
docs
- Updated development-models.md with a new section on Manifest Builder (PR #3788)
53.14.1 - January 19, 2022
Fixed
salesforcedx-vscode-apex-replay-debugger
- Backend changes to set up Anonymous Apex in replay debugging (PR #3758)
53.13.0 - January 13, 2022
Added
salesforcedx-vscode-apex
- Identify test class from uri (PR #3751)
Fixed
docs
- Updates to reflect runtime restrictions (PR #3741)
salesforcedx-vscode-apex
- Prevent local java runtime in project (PR #3730)
53.12.0 - January 5, 2022
Added
salesforcedx-vscode-core
- Add ability to remove expired orgs from the org list (PR #3732)
53.8.0 - December 16, 2021
Added
salesforcedx-vscode-apex
- Enable use of anonymous Apex execution code...
Release v54.8.0
54.8.0 - April 13, 2022
Fixed
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
We now consume the latest lightning-language-server packages, which fixes the textDocument/hover error when the package incorrectly parsed the content of .js
files (PR #4003). Fixes Issue #3929.
salesforcedx-vscode-core
We now strip leading and trailing white spaces from the project name when you create a project using the SFDX: Create Project
command. (PR #3950). Fixes Issue #2605
54.7.0 - April 6, 2022
Added
salesforcedx-vscode-core
- Right-click and run the new SFDX: Rename Component command to quickly rename all the files of an LWC component (
js, html, css, js-meta.xml
file types) or an Aura component (auradoc, cmp, cmp-meta.xml, css, design, svg, contoller, helper, renderer, js
file types) using a single command (PR #3923).
54.6.1 - March 23, 2022
Fixed
- Fixed inconsistent published package versions caused by issues with the availability of the VSCode Marketplace during publish of v54.6.0.
docs
54.6.0 - March 23, 2022
Added
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
- Took advantage of recent updates to lightning langauage server packages and the iterator template directive. Improved directive descriptions. (PR #3891)
salesforcedx-vscode-lwc
- Added a new debug configuration for creating LWC jest tests so that you can easily write JavaScript tests for your Lightning web components. (PR #3920)
Fixed
docs
- Updated Java Setup instructions to include instructions for JDK 17. (PR #3909)
salesforcedx-utils-vscode, salesforcedx-vscode-apex, salesforcedx-vscode-apex-replay-debugger, salesforcedx-vscode-soql
salesforcedx-vscode-core
- Retrieve components within folders for metadata types such as Reports, Dashboards, Documents, and EmailTemplates. Before this update, it wasn't possible to retrieve individual component metadata from within folders. (PR #3892)
salesforcedx-vscode-lightning, salesforcedx-vscode-lwc
54.5.0 - March 14, 2022
Fixed
salesforcedx-vscode-core
- We’ve updated the library that supports Salesforce Templates commands in VS Code so that it now uses API version 54.0 when generating new metadata from our standard templates.(PR #3749)
54.4.1 - March 10, 2022
Fixed
salesforcedx-vscode-core, salesforcedx-vscode-apex
- We reverted the source-deploy-retrieve library to v5.12.2 because it was sometimes failing on OSX Monterey.
54.4.0 - March 9, 2022
Fixed
salesforcedx-vscode-core
- We fixed an issue with the SFDX: Diff Folder Against Org command so that it now diffs objects against orgs correctly. (PR #3876)
54.3.0 - March 3, 2022
Added
salesforcedx-vscode-core
-
We’ve made the functionality of older versions of some commands available for you to use with your existing scratch orgs. Use these legacy commands so you don’t run into issues with their newer versions:
SFDX: Pull Source from Default Scratch Org (Legacy)
SFDX: Pull Source from Default Scratch Org and Override Conflicts (Legacy)
SFDX: Push Source to Default Scratch Org (Legacy)
SFDX: Push Source to Default Scratch Org and Override Conflicts (Legacy) and
SFDX: View All Changes (Local and in Default Scratch Org) (Legacy) (PR #3839)
salesforcedx-vscode-lightning & salesforcedx-vscode-lwc
- Autocompletion is now available for bracket syntax
'{}'
in HTML files.(PR #3865)
Fixed
docs
salesforcedx-vscode-expanded
salesforcedx-vscode-apex
salesforcedx-vscode
- We now support JDK version 17 in addition to versions 8 and 11. (PR #3860)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #3869)
54.2.0 - February 24, 2022
Added
salesforcedx-vscode
- Run the new Start Function in Container command to run a Salesforce Function in a Docker container. The old command, Start Function now runs a function locally. (PR #3838, PR #3856)
Fixed
salesforcedx-vscode
- We resolved the issue with the Diff Folder Against Org command being visible from the command palette even when an SFDX project wasn’t open. (PR #3843).
salesforcedx-vscode-apex
- We removed some unessential Apex classes from the Apex LSP .jar file. (PR #3844)
54.0.0 - February 15, 2022
Added
salesforcedx-vscode
- Run the updated Launch Apex Replay Debugger with Current File to launch the Apex Replay Debugger from an Apex test file, an Anonymous Apex file, or an Apex log file. Previously, you could launch the Apex Replay Debugger only from an Apex log file. Also, we’ve simplified both the setup and execution of the command. You’re no longer required to create a launch configuration (launch.json) to run the Apex Replay Debugger, and you can debug your code with fewer steps. (PR #3779, PR #3827).
Fixed
salesforcedx-vscode
-
The Generate Manifest File doesn’t show up as an option when you right-click on components within metadata types. Previously, the command showed up incorrectly even though it wasn’t executable (PR #3818).
-
The Execute Anonymous Apex code lens is now working as expected (PR #3819).
-
We fixed a broken video link in documentation (PR #3817).
53.16.0 - February 2, 2022
Added
salesforcedx-vscode-core
- The new Manifest Builder feature has been added to automatically generate a manifest file for a given set of metadata components instead of editing the package.xml file manually (PR #3784)
docs
- Updated development-models.md with a new section on Manifest Builder (PR #3788)
53.14.1 - January 19, 2022
Fixed
salesforcedx-vscode-apex-replay-debugger
- Backend changes to set up Anonymous Apex in replay debugging (PR #3758)
53.13.0 - January 13, 2022
Added
salesforcedx-vscode-apex
- Identify test class from uri (PR #3751)
Fixed
docs
- Updates to reflect runtime restrictions (PR #3741)
salesforcedx-vscode-apex
- Prevent local java runtime in project (PR #3730)
53.12.0 - January 5, 2022
Added
salesforcedx-vscode-core
- Add ability to remove expired orgs from the org list (PR #3732)
53.8.0 - December 16, 2021
Added
salesforcedx-vscode-apex
- Enable use of anonymous Apex execution codelens (PR #3688)
Fixed
salesforcedx-vscode-core
-
Fix org browser to show retrieve source action for sobjects (PR #3697)
-
Fix org browser to display nested items such as Email Templates, Dashboards, Documents and Reports (PR #3685)
53.7.0 - December 9, 2021
Fixed
docs
- Fix broken doc links (PR #3665)
salesforcedx-vscode-core
-
Retrieve field data for a custom object type (PR #3661)
-
Ability...