Posts

2.3.6.2 release notes

2.3.6.2 Issue 2798  - Summer '25 / API v64.0 update Updated the SOAP client for API v64.0. Updated the API version used for primary communication with Salesforce APIs to 64.0. Added 64.0 as an available API version number for configured connections. Updated  metadata.xsd  based on the API v64.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in Summer '25. Updated the bundled  completions?type=apex  Tooling REST API response to be based on the API v64.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '25 changes. Updated the bundled SLDS CSS and SVG icons to 2.27.1. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Added support for LWC local dev preview for a  single LWC component . This manifests as another context action,  Start local development server for...

2.3.6.1 release notes

2.3.6.1 Please be aware that my summer holiday outage will occur over the next two weeks, and I will transition temporarily into sales-/support-only mode. There will be no planned weekly releases during this time, but once complete, I will return to the standard weekly release cadence starting with an update for  Salesforce Summer '25 / API v64.0  followed by the typical mix of features, enhancements, fixes, and improvements. Of course, if critical issues arise during this outage that warrant a hotfix or similar time-sensitive response, I will address them ASAP. Issue 2797  - Retrieval in a metadata format project no longer fails completely if the retrieved archive includes files with names that are not valid in the local filesystem. Instead, files with valid names are extracted, and those with invalid names are reported to the user. Added support for Agentforce for Developers-assisted ApexDoc generation: For Apex declarations without an ApexDoc comment, IC now offers a n...

2.3.6.0 release notes

2.3.6.0 Issue 2784  - API-based deployment is now disabled/bypassed when  sfdx-project.json  includes  string replacement  configuration. Note that IC doesn't try to determine whether or not the specific files requested for deployment would have string replacements based on that configuration. If any string replacement configuration is present in  sfdx-project.json ,  all  deployments are performed using the Salesforce CLI. Issue 2786  - Improved the behavior when creating or executing a Salesforce API-specific HTTP client request and invalid connections are present. Issue 2793  - Added a few missing PMD distribution jars to the  PMD Salesforce  inspection's runtime classpath. Issue 2794  - Fixed an incorrect utility method import that could result in incomplete generation of  .illuminatedCloud/lwc/types  module type definition files when LSP4IJ was not installed and enabled. Implemented several small enhancement...

2.3.5.9 release notes

2.3.5.9 Issue 2741  - Added Salesforce module import targets to the  Navigate | Related Symbol  list for LWC JavaScript and TypeScript files in Community Edition IDEs as well as the support for commercial IDEs included in the previous build. Issue 2785  - Integrated  Salesforce Code Analyzer 5  into IC. A demonstration video is available  here . The integration includes: A bulk code inspection,  Salesforce Code Analyzer , that executes Code Analyzer on the specified scope and presents results in the IDE's  Problems  tool window. A  near -real-time external annotator that executes Code Analyzer on the file in the focused editor and presents results directly in the editor alongside other static code analysis results. Note that " near -real-time" means that, as an external process running multiple concurrent static code analysis engines, Code Analyzer typically takes several seconds to yield results for even a single file. Consequently...

2.3.5.8 release notes

2.3.5.8 Issue 2468  - Implemented a custom diff tool for Salesforce Flow metadata,  Flow diagram side-by-side viewer , that displays Mermaid-based diagrams for two Flow revisions or files. This can be accessed in the IDE's internal diff viewer using the diff tool drop-down as an alternative to the standard  Side-by-side viewer  and  Unified viewer  options, and are available in any context in which the IDE's internal diff viewer can be used, e.g., VCS version comparison, Local History version comparison, and comparison of two explicit  *.flow  project files. Please be aware of the following limitations in the current implementation: This diff tool will  not  be used if the IDE is configured for an external diff tool for the  Default  file type. Differences between the two Flow revisions/files are not currently annotated explicitly. The diagrams are shown for the respective revisions/files just as they would be in the Flow previ...

2.3.5.7 release notes

2.3.5.7 Issue 364  - Extensive SOSL support improvements (demo video available  here ) including: Added a  SOSL Query  tool window with effectively the same features as the  SOQL Query  tool window (and, for the most part, the  Anonymous Apex  tool window). Just as with SOQL query results, SOSL query results are presented in table-based and tree-based views, and those results can be copied to the clipboard as tabular and JSON data respectively. This new tool window is accessible via keyboard as  Ctrl+Shift+Alt+X  on all operating systems and  Cmd+Shift+Opt+X  on Mac Added a  SOSL Query  file type that is associated with the  *.sosl  file extension. Context actions are available in these files to open and execute the script — or the selected subset of the script — in the  SOSL Query  tool window. Added support for syntax highlighting, code completion, and other editing features in SOSL search expres...

2.3.5.6 release notes

2.3.5.6 Issue 745  - Added support for IDE  scopes  in the bulk metadata deployment/retrieval/removal dialog's  Contents  selector. The original values —  Module ,  Module + Dependencies ,  Project ,  Context , and  Custom  — are still available as the top-most values, but now all predefined, provider-based, and user-defined scopes are included as long as they don't duplicate the original scopes and are applicable to full project metadata files. The most recent selected value for  Contents  is still retained across operations even if it's scope-based. Issue 2699  - Prospective(/hopeful) fix for the issue with Flow preview diagrams not displaying consistently in 2024.2+. Please let me know if you continue to see this issue after updating to this build or higher. Issue 2767  - Fixed an issue with generation of LWC TypeScript stubs for  @AuraEnabled  Apex symbols in projects with a namespace. Issue 2770 ...