Illuminated Cloud Announcements

2.3.1.9 Issue 2584  - Summer '24 / API v61.0 updates Updated all SOAP API clients to be based on the API v61.0 WSDLs. Updated the API version used for primary communication with Salesforce APIs to 61.0. Added 61.0 as an available API version number for configured connections. Updated the OST version number to prompt regeneration for system API changes in API v60.0. Updated the bundled  completions?type=apex  Tooling REST API response to be based on the API v61.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '24 changes. Updated the bundled SLDS CSS and SVG icons to 2.24.2. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Added full support for the new Apex  @InvocableVariable  annotation  DefaultValue  and  PlaceholderText  attributes. I've also updated the Apex Annotation and Modifier Agreement code in...

2.3.1.8 Reissue of  2.3.1.7  with the fix for a potential error resulting from a stale cache entry when collecting transitive dependencies/dependents for Apex unit test execution and/or coverage analysis. 

  2.3.1.7 JetBrains has issued patch-level updates for all of their 2023.1+ IDEs to fix a  security issue . Please see the linked information for details, but the short version is that the security issue should only affect those using JeBrains' GitHub pull request integration. Nonetheless, I  strongly  encourage all users update to a JetBrains IDE version with this fix ASAP. More improvements to the recent dependencies-/dependents-based enhancements for Apex unit test execution and code coverage analysis: All transitive dependencies and dependents are now collected at the member-level instead of the file-level. Again, this means that the resulting set of dependencies/dependents should be as small and focused as possible short of performing runtime data flow analysis. When using the new "changed-only" features, this should ultimately mean less time spent waiting for unrelated unit tests to execute and a more focused view of impacted code coverage. Added many more meta...

2.3.1.6 This week's build is a small set of bug fixes. I'm in final testing of the last anticipated major round of Apex unit testing and code coverage dependency/dependent-related enhancements. They didn't quite make this week's build but should be in great shape for next week's. Issue 2572  - Fixed an issue with SOQL query count validation for pure aggregate queries that return a single row. Issue 2576  - Fixed an NPE during expression type evaluation reported by a user. Issue 2580  - Improved original error message retention when handling caught exceptions during PMD execution. Fixed a recently-introduced regression where file delete handler logic wasn't firing properly. This would result in removal of supporting meta.xml files and the corresponding metadata from the server not happening when metadata files were removed locally from the project. Added another user-reported variant of  FIELD_INTEGRITY_EXCEPTION  when trying to deploy an LWC JavaScript file via ...

2.3.1.5 Implemented several improvements to the recent dependencies-/dependents-based enhancements for Apex unit test execution and code coverage analysis: Transitive dependencies are now collected at the member-level instead of the file-level. This effectively means that the resulting set of dependencies should be as small and focused as possible short of performing runtime data flow analysis. Trigger logic relationships are now properly included when collecting transitive dependencies and dependents. See below for more information about the general improvements around the relationships between DML statements (both static and dynamic) and triggers included in this build. Added support for dependents unit test run configurations from Apex triggers. Minor cosmetic improvements regarding how dependency relationships are displayed in the coverage view when filtering by VCS changes. Note that I am also currently wrapping up another set of  major  improvements in this area to inclu...

2.3.1.4 (hotfix) This is effectively  2.3.1.3  with a hotfix for the customer-identified deployment issue described below. Issue 2570  - Fixed an issue that would result in  Check Only  (aka, "Dry Run") deployments actually updating the requested metadata in source format projects. This was due to the  sfdx  command's  -c  argument not being properly migrated to the corresponding  sf  command's  --dry-run  argument in the recent update to use the newer command set.

  2.3.1.3 I've posted a  demonstration video  detailing all of the recent Apex unit testing and code coverage enhancements including those described below. Issue 822  - Implemented another round of improvements around execution of dependent Apex unit tests. Now most Apex unit test run configuration types can be optionally configured as  Changed Only  which will execute only the Apex unit test classes from the run configuration that are either themselves changed or are (transitive) dependents of changed production (i.e., non-test) Apex source files. To be specific,  changed  in this context is with regard to the project's configured  version control system , so  Changed Only  is applicable only to VCS-enabled projects. Enabling it for a run configuration in a non-VCS-enabled project will simply result in all of that run configuration's tests being executed as if that option was disabled. The  Changed Only  option can be ena...