Illuminated Cloud Announcements

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

2.3.4.4 Issue 2674  - Agentforce for Developers API failure details should now be more clearly raised to the end user so that, instead of seeing something like: Status 400 returned trying to retrieve ...: Bad Request the user will now see something like: BAD_ARGUMENT (E30021) - Error in plugin codegen: INVALID_ARGUMENT: EGptForDevsPlugin: prompt is beyond the limit, ... Issue 2712  - Prospective fix for a  ConcurrentModificationException  observed by a user after first opening a project. Issue 2718  - Fixed the spelling of  dismissible  in  lightning/toast.ToastConfig . Updated messages for bundled code inspections, intentions/quick-fixes, etc., to use more extensive formatting so that things like symbolic names stand out more clearly. Other related minor fixes and improvements. Once again, this build includes broad improvements and simplifications based on newer Java language level features and the corresponding code inspections, and once again, ...

2.3.4.3 Issue 2666  - Fixed an issue with SOQL  FROM  type resolution in a parenthesized set nested within a SOQL sub-query. Enhanced the SOQL query code inspection to detect nested sub-queries in  WHERE  clauses against the same type queried by any ancestor query. This would otherwise have resulted in an error that wasn't reported until deployment-time. Fixed a potential deadlock that could occur when compiling LWC TypeScript files in commercial JetBrains IDEs as part of a source-tracked push deployment immediately following scratch org creation. Improved support for JavaScript template string literals, i.e., those that begin and end with backticks ( `...` ), in Community Edition IDEs. Fixed a potential NPE that could occur when editing JavaScript/TypeScript string literals in top-level script statements in Community Edition IDEs. Removed a workaround for a very old backward-incompatible Salesforce CLI change that should no longer be needed and had caused a sma...

2.3.4.2 Issue 2704  - Prospective fix for a type name resolution issue that can occur when resolution occurs before the type name has been properly indexed. Issue 2707  - Prospective fix for an  IndexNotReadyException  that could occur when the project is indexing and LWC HTML templates are opened in editor tabs in a commercial JetBrains IDE. Added JavaScript/TypeScript live templates and surround templates for those using Community Edition IDEs. Most of these templates are direct ports of the standard templates for those languages from the JetBrains commercial IDEs, though obviously they're not quite as contextually-aware as their commercial counterparts. Still, when used with LSP4IJ, they work quite well. Rather than enumerate them all here, I'd recommend looking at  Settings | Editor | Live Templates | JavaScript / JavaScript Testing . Improved handling of unbalanced nested empty braces/brackets/parentheses when editing JavaScript, TypeScript, and CSS files i...

2.3.4.1 Issue 2667  - Fixed a regression in the Apex extract method refactoring introduced in  2.3.3.8  where the required formal parameters for the extracted method would not be inferred properly. Issue 2682  - Added the following application-level configuration options — both  enabled by default  — to  Illuminated Cloud | Configure Application | Other | Lightning Web Components : Automatically update .gitignore  - When enabled, IC-specific entries are automatically added to  .gitignore  if present. Automatically update .forceignore  - When enabled, IC-specific entries are automatically added to  .forceignore  if present. Issue 2690  - Implemented a set of prospective performance optimizations for how LWC custom component definitions are enumerated, particularly in projects with large numbers of custom LWC components. Issue 2693  (redux) - Broadened support for  export default  as a separate statement....