Illuminated Cloud Announcements

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 results of porting from JavaScript to TypeScript. Again, this is still an early version of

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. Barring unforeseen circum

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

2.3.3.4 Reissue of  2.3.3.3  with a hotfix for an issue where the new Local Development Server run configuration producer would cause actions from other run configuration producers — including those for Apex unit test execution — not to be added properly. Sincere apologies for those affected by this temporary regression.

2.3.3.3 Issue 2632  - Winter '25 / API v62.0 updates Updated the API version used for primary communication with Salesforce APIs to 62.0. Added 62.0 as an available API version number for configured connections. Updated the OST version number to prompt regeneration for system API changes in API v62.0. Updated the bundled  completions?type=apex  Tooling REST API response to be based on the API v62.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Winter '25 changes. Updated the bundled SLDS CSS and SVG icons to 2.25.1. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Fully integrated the new  Local Development Server  feature. I've recorded a  demonstration video  showing the features of this integration including the following: Added a new run configuration type for integrated execution of the local development server from within Illuminated C

2.3.3.2 Issue 2640  - When a new Apex unit test run configuration is added from the bulk deployment dialog, it is now automatically selected as the active configuration for unit test execution for that deployment. Issue 2645  - A handful of users have been having issues with IC not finding all of their projects' Apex unit test classes after updating to  2.3.3.1 . It appears that a full index/cache rebuild via  File | Invalidate Caches  may help, but I've also implemented a prospective fix for the issue in this build. If you're still seeing this problem in the build or later even after an indexes/caches rebuild, please let me know so that I can work with you to get diagnostic information. Issue 2648  - Fixed an issue that could result in static resources not being shown correctly in metadata format projects. Implemented several improvements to the new  Agentforce for Developers  feature integration: Made the feature significantly more configurable, specifically in terms of w

2.3.3.1 Issue 2637  - Added full support for  Agentforce for Developers  in Illuminated Cloud for Apex and LWC. A pretty comprehensive  demonstration video  is available. In general, it works exactly as described in the linked document including: Multi-turn chat with Dev Assistant  - Dev Assistant has been integrated as a new IDE tool window, by default docked to the top-left portion of the IDE window. It can also be accessed via the keyboard shortcut  Ctrl+Alt+Shift+W  (all OSes including Mac) or  Cmd+Opt+Shift+W  (Mac only). Dev Assistant supports natural language requests as well as the following "slash commands": /explain  - Explains the code in the active editor if the  Use the selected editor  option is enabled, or the code from the most recent Dev Assistant response if disabled. /document  - Creates documentation for the code in the active editor if the  Use the selected editor  option is enabled, or the code from the most recent Dev Assistant response if disabled. /te