Illuminated Cloud Announcements

2.3.5.2 Note that this week's build is a smaller, tactical set of fixes and enhancements as I have a scheduled outage the latter part of the week and weekend. Issue 2732  - A few more threading improvements/fixes. Issue 2734  - Added a  Cancel  option to the Apex unit test execution debug and profile logging level selection dialogs. Issue 2761  - Fixed an issue with automatic Metadata API-based retries of failed Tooling API-based LWC deployments. Prospective fix for a possible  ConcurrentModificationException  while enumerating accessible body declarations.  

2.3.5.1 Issue 2732  - Implemented more threading performance improvements. As before, this won't be the last of them, but hopefully this will address a few additional use cases. Issue 2751  - Added some missing values for the Aura  lightning:select  component's  variant  attribute. Issue 2752  - Added support for the  @SuppressWarnings  annotation on local variables, formal parameters, and caught exceptions. This includes Apex parser grammar support, code formatter support, support for adding suppressions via suppression quick fixes on all three when issues are reported against them, and of course respecting those suppressions in the IDE. Note that this annotation is not supported by the Salesforce Apex compiler on  for  loop variables, so IC supports the same behavior. Issue 2754  - Prospective fix for a deadlock while refreshing CLI-based connections during a bulk metadata operation. Issue 2755  - Fixed an issue with the...

2.3.5.0 Issue 2732  - Since updating to version 2024.3+ of your JetBrains IDE, you may have seen messages like "'Illuminated Cloud 2' might be slowing things down". This is a new message added by JetBrains to help identify behaviors in plugins — both first-party and third-party — that are not properly offloading long(-ish)-running behaviors to background threads. This doesn't mean that anything that has actually changed for the worse in IC (or whatever plugin/subsystem you might see attributed with this message). It just means that less-than-ideal existing behaviors are now being reported to help identify and resolve them. In this build, I've refactored IC's main long-running operations — metadata deployment, retrieval, and removal; offline symbol table generation; Salesforce CLI execution; anonymous Apex and SOQL query execution; etc. — so that they are moved to a background thread and, if appropriate, a progress indicator as quickly as possible after bei...

2.3.4.9 Issue 986  - Added classifications for Apex usages including: Declaration types Method return types Type parameters Type and method inheritance relationships Instance and array constructions via the  new  operator Explicit constructor invocations via  super()  and  this() Method invocations Field/property/local variable reads Field/property/local variable writes Class nested type accesses Class static member accesses Runtime type checks via the  instanceof  operator Type casts Query usages by clause type DML usages — both static and dynamic — by operation type Visualforce/Aura/LWC-based usages XML-based usages Let me know if you still see usages reported as  Unclassified  for which there should be clear classification, or if you see things classified incorrectly. Also, the  Show Read Access  and  Show Write Access  toggles in the various usage views should now filter the results accordingly. Issue 2699  -...

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...