Illuminated Cloud Announcements

2.3.4.8 Issue 2727  - Spring '25 / API v63.0 update completion It looks like the last instances have been updated to Spring '25 / API v63.0, so this build includes updates for the SOAP and REST API clients to communicate using that version. If you see errors like  UNSUPPORTED_API_VERSION , please revert to the previous release and let me know your org and instance IDs. This build includes the following Spring '25 / API v63.0 changes: Updated the SOAP client for API v63.0. Updated the API version used for primary communication with Salesforce APIs to 63.0. Updated  metadata.xsd  based on the API v63.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in API v63.0. Issue 2716  - Integrated the  SLDS Validator  static code analyzer into IC. This is considered a  beta-level  feature due to the known issues described below. A demonstration video is available  here . The SLDS Validator is deli...

2.3.4.7 Issue 2727  - Spring '25 / API v63.0 updates NOTE:  Not all instances have been updated to Spring '25 at this point. At least one is scheduled for update next weekend. As a result, this Spring '25 update of IC does not yet change the SOAP and REST endpoint API version to v63.0. As soon as all instances are confirmed to be on the latest API version — hopefully after next weekend — I will release a build of IC that uses that API version for all communications with the Salesforce servers. This seasonal platform release update build includes the following changes for Spring '25: Added 63.0 as an available API version number for configured connections. While this doesn't affect the API version used by IC's SOAP and REST client, it is used for generation of new metadata files that specify an API version and for the  Inconsistent API Version  code inspection if so configured. Updated the OST version number to prompt regeneration for system API changes in Spring...

2.3.4.6 This is a small bug fix update as I've been working on the Spring '25 updates for release on next Monday and helping to put the finishing touches on the LSP4IJ 0.10.0 release. Issue 2726  - IC now restricts checks for LWC test files to  **/lwc/**/__tests__/**  and  **/lwc/**/__utam__/** . This should resolve deployment issues for those who, for example, store Apex unit test class files under  classes/__tests__ . Note that such users will also want to make sure that a more specific pattern is used in  .forceignore , e.g.,  **/lwc/**/__tests__/**  instead of just  **/__tests__/** . Fixed an issue with creation of new native connections to production organizations where  Ensure field read access  would be enabled by default and committed without any type of warning. This change also includes more extensive safeguards for verification of potentially unsafe connection configurations for "sacred" connections such as those to produ...

2.3.4.5 Issue 2717  - Code completion and reference resolution now properly includes custom properties from the bundled SLDS CSS. Issue 2720  - REST API calls now properly use the IDE's SSL certificate configuration. Issue 2723  - Reverted  2.3.4.4  formatting changes to inspections and intentions that are attributed at the file-level because such formatting is not rendered properly there. This will resolve issues where, for example, the  Inconsistent API Version  inspection header banner would include raw HTML markup. Issue 2724  - IC no longer recommends adding the  static  modifier to  protected  fields since that's an invalid combination in Apex. I also updated the Apex  Annotation and Modifier Agreement  code inspection to flag the combination of  protected  and  static  modifiers as an error so that this is detected locally in the editor and not deferred until deployment-time. These reported ...