Illuminated Cloud Announcements

  2.2.7.3  - reissue of  2.2.7.2  with hotfix for  issue 2380 . Issue 2380  - Fixed what appears to be a corner-case issue where the batch deploy/retrieve/delete dialog would fail when local foldered metadata files are found in a specific state. NOTE:  I've also noticed an intermittent issue when running some CLI commands where the JSON output of the command is malformed due to an error rolling the  sf.log  file. The specific command that seems to produce this most often for me is  force:project:create . In that situation, the resulting project is created, but the new project wizard stumbles due to the perceived issue. It's safe to open the created project and proceed with its configuration. I have logged this issue with Salesforce as  2209 .

  2.2.7.2 Issue 2358  - Summer '23 / API v58.0 updates Updated all SOAP API clients to be based on the API v58.0 WSDLs. Updated the API version used for primary communication with Salesforce APIs to 58.0. Added 58.0 as an available API version number for configured connections. Updated  metadata.xsd  used for validation and code completion in metadata XML files to API v58.0. Updated the OST version number to prompt regeneration for system API changes in API v58.0. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '23 changes. Updated the bundled SLDS CSS and SVG icons to 2.21.1. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Added support for SOQL queries with up to five levels of nesting when executed standalone. Nested SOQL query depth is now validated by the  SOQL Query  code inspection, allowing up to five levels in standalone usa...

  2.2.7.1 NOTE:  I have been seeing intermittent failures with the Salesforce  completions?type=apex  Tooling REST API that is used during offline symbol table generation. These are reported as generic  HTTP 500 / Server Error  and seem to resolve themselves on repeated OST generation attempts or attempts after doing just about anything in the org, e.g., performing a successful deployment. I have made Salesforce aware of these failures and they are investigating, but I also wanted to ensure that users were also aware of them and possible workarounds until the issues are properly resolved. Issue 2367  - Added support for the  DigitalExperienceBundle  metadata type. Note that this explicitly ignores the  DigitalExperience  sub-type for purposes of deployment and retrieval at present and operates at the bundle-level only. Issue 2368  - Fixed an issue where Apex string literals wouldn't be properly escaped when used directly with t...

  2.2.7.0 Issue 2346  - Added support for implementing  Database.Batchable  with the  start()  method signature that returns  Database.QueryLocator  when the type parameter for the implemented interface is specifically  <SObject> . Note that both return signatures are offered for implementation, but only one can be implemented. While I was in there, I also tightened up the surrounding whitespace when generating implemented/overridden methods and improved initial selection of the first return statement expression in generated implemented/overridden methods. Issue 2360  - Fixed an issue where the  Open/Execute/Debug Anonymous Apex/SOQL Query  actions could end up using a stale version of the original file if there were unsaved changes. Now any pending changes are saved before the contents are transferred to the respective tool window. Issue 2363  - Added  Schema.Network  to the resolution strategy that alread...