Illuminated Cloud Announcements

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

2.3.4.0 Issue 2693  - Added support for  export default  as a separate statement from the actual type declaration. Issue 2694  - Inheritance should now be properly detected for  NavigationMixin s. Issue 2697  - Prospective fix for a  PsiInvalidElementAccessException  when editing large Apex files. Added support for  Navigate | Type Declaration  in Apex for declaration name identifiers and non- void  expressions. Implemented a few additional improvements/fixes for JavaScript/TypeScript LWC dev in Community Edition IDEs: Fixed an issue with detection of property read accessors in JavaScript/TypeScript LWC files. Note that inherited body declarations are still not detected in Community Edition IDEs. Fixed an issue with pseudo-elements created for body declarations in JavaScript/TypeScript LWC files. This fix, when coupled with an enhancement I've contributed to LSP4IJ, enables cross-language reference resolution when used with LSP4IJ i...

2.3.3.9 Issue 2685  - Updated the data type for  lightning-datatable.wrap-table-header  to be an enumerated type instead of a  boolean . Issue 2688  - Fixed an issue with the translation from Apex  Map  to the corresponding TypeScript ambient import definition for an  @AuraEnabled  symbol that uses a  Map  for one of its types. Note that  Map  and  Set  are translated into  any  because only state is transferred, not behavior. Issue 2689  - More defensive against potential  IndexNotReadyException  in 2024.3 when enumerating JavaScript/TypeScript fields and properties. Integrated  LSP4IJ  for those who use Illuminated Cloud with a free JetBrains Community Edition IDE to provide a  significantly improved editor experience  for JavaScript, TypeScript, and CSS, particularly in LWC source files. LSP4IJ is a  free, open source  plugin from Red Hat for all JetBrains...

2.3.3.8 Issue 2667  - Fixed an issue with the Apex extract method refactoring when used on statements from a static initializer. Issue 2668  - Fixed an issue with resolution in SOQL  TYPEOF/WHEN  clauses in sub-queries. Issue 2670  - Added specific formal parameter names to  System.WebServiceMock.doInvoke()  in the OST. Note that the OST must be regenerated to see the effect of this change. Issue 2676  - Fixed an issue with the Structure View tool window that was introduced in 2024.3 due to a change in the threading model where it would either show no contents or raise an error. Issue 2681  - Added a new configuration option to disable the new LWC TypeScript support feature. This option is available as  Illuminated Cloud | Configure Application | Other | Lightning Web Components | Lightning Web Components TypeScript support (beta)  and is  enabled by default . When disabled: The  TypeScript  checkbox is not displayed ...

2.3.3.7 Removed support for JetBrains 2023.3 IDEs . Unfortunately that version has an increasing number of incompatibilities with recent big features including Agentforce for Developers and LWC TypeScript support described below. Issue 1921  - Added  beta-level  support for  Lightning Web Components development in TypeScript . I've posted a  video demonstration  of the feature. It's rather lengthy, but I've provided direct links to key topics in the video description. You can access the ported fork of the  ebikes-lwc  repository used in the video demonstration  here , and similarly you can access the ported fork of the  dreamhouse-lwc  repository  here  and the ported fork of the  lwc-recipes  repository  here  . In each forked repository, the  main  branch is effectively the same as the original but with a fully-configured IC project included, and the  ic_lwc_ts  branch includes the...

2.3.3.6 Enabled compatibility with JetBrains' upcoming  2024.3  releases. As usual, I recommend that all users stay on a fully-supported JetBrains IDE release as there is always a slim chance of minor-but-breaking changes in JetBrains' final builds leading up to the 2024.3 release, but assuming that doesn't happen, 2024.3 should be good to go starting with this build. If any breaking changes are found in subsequent JetBrains builds, I will issue an IC2 hotfix ASAP. Issue 2669  - Fixed a potential performance issue with the Agentforce for Developers Dev Assistant when  Include referenced schema  is enabled and local custom object metadata files do not include  <label>...</label>  information. Fixed an issue that could occur when a suppression comment is found at the very beginning of an Apex source file. Also note that the lack of usual weekly releases over the past few weeks is due to the time required to get the next big feature ready. Bar...

2.3.3.5 Issue 2649  - After exporting SOQL query results to a CSV file, the resulting file is only opened in the IDE if it's under the  maximum file size limit  for IDE features ( idea.max.intellisense.filesize ). Otherwise the file is shown in the host operating system's file manager. A few additional Winter '25 updates: Updated the bundled SOAP API clients to API v62.0. Updated the bundled  metadata.xsd  used for validation and completion in XML metadata files to API v62.0. When starting the local development server with no Lightning Experience application or Experience Bundle site, the user was being presented with a command-line-based application selector. Now IC presents a first-class application selector, retaining and defaulting the previously-selected value across invocations. As a result, there is no longer a notion of an "All apps" run configuration. Instead such run configurations are now called "Selected LWC app". Implemented a better fix for...