Illuminated Cloud Announcements

2.3.6.7 Issue 2725  - It's now possible to add a  tsconfig.overrides.json  file as a peer to the generated  tsconfig.json  and  tsconfig.compile.json  files under a project's  lwc  directories. When present, this file is automatically added to the generated files'  extends  lists to allow customization of TypeScript compiler behavior. While the order in which these files are processed should help prevent overriding options which are critical for IC's core TypeScript compilation functionality, if you make a change that does result in broken or incorrect compiler output, please revert that change and let me know so I can help further insulate against unintentional issues. Issue 2800  - Added support for inlining of Flow text templates at their point-of-use. Note that when these are rich text, the raw HTML is escaped and displayed inline. I'd also like to add support for inlining of other resource types such as choices, choice col...

2.3.6.6 Issue 2812  - Fixed a few issues with source format project creation resulting from recent changes to the Salesforce CLI's project templates. Issue 2813  - Flows are now opened in the Salesforce Setup Web UIs — both classic and Lightning — via the flow definition just as if the user had opened the Flow screen from the Setup UI itself. LWC JavaScript/TypeScript methods which are referenced by HTML braced expressions are no longer flagged as candidates to be denoted  static  as that can break the HTML-based references. Note that this change only affects commercial IDEs. Fixed a potential issue with the temporary Salesforce Code Analyzer config files used to disable redundant engines and rules.  

2.3.6.5 Added support for  SLDS Linter . SLDS Linter is, for all intents and purposes, a set of rules for the standard  ESLint  and  Stylelint  static code analyzers, and that's exactly how it's integrated into Illuminated Cloud. In commercial JetBrains IDEs, the first-class  ESLint  and  Stylelint  code inspections are used. In Community Edition JetBrains IDEs, the  ESLint  and  Stylelint  language servers are used via  LSP4IJ . Note that LSP4IJ version 0.14.3 is required for these two language servers, and that is unreleased at the time of this writing. Please install a  nightly build  if necessary. A demonstration video is available  here . IC helps to install and configure all required components via  Settings | Editor | Inspections | Salesforce | SLDS Linter . While delivered as a code inspection, that entry is really just a proxy to help get everything installed and configured properly includ...

2.3.6.4 Added support for multiple context files in the Agentforce for Developers  Dev Assistant  tool window. The  Use the selected editor  option is still used to add the file in the selected editor tab as a context file, and there is now an  Additional context files  expandable text field and companion  Add context file  button to add and manage other files from the project that should be included in the generated prompt for context. Note that the Agentforce API does limit the prompt size, so adding large numbers of context files and/or large context files may result in errors during prompt execution. Added support for  ESLint  integration in JetBrains  Community Edition  IDEs via LSP4IJ 0.14.3 (not yet released, but you can install a  nightly build  to play with it now) and Microsoft's  ESLint language server : If ESLint is integrated via LSP4IJ and the Salesforce Code Analyzer 5 integration is configured to ...

Today marks 10 years since the first public release of Illuminated Cloud. In many ways, that's honestly difficult for me to comprehend, though in some ways, it seems about right. I still vividly (or perhaps hazily ) recall the first few days after that initial release when I was learning — literally hour by hour — that all of the “extensive testing” I'd done locally was in no way a proper preparation for the wide array of machine and org configurations against which IC would be used out in the wild. The first week specifically was pretty much a constant stream of hotfixes. However, what was truly encouraging — in spite of that mad 'round-the-clock scramble — was the supportive nature of the feedback that I was getting from the Salesforce developer community. Instead of "This is broken. Why did you even release it in this state?", I was hearing "I really like what I’m seeing and look forward to getting fixes for the things that aren’t working just yet." ...

2.3.6.3 Issue 2797  - Improved messaging when files could not be extracted from a metadata retrieval archive because their filenames would be invalid for the local file system. Now these issues are included in the  Messages  tool window retrieval status in addition to the toaster pop-up notification. Issue 2801  - Fixed an issue where an editor's active  Find  text field would receive focus upon switching active editors when tabbed editors are enabled. Issue 2810  - Fixed an issue where bulk Apex debug log delete could not be cancelled. Bulk delete progress is now reported in a more detailed manner as well. Added support for the Apex  @JsonProperty  annotation on fields and properties. Note that I've been unable to find any concrete documentation for this annotation, so right now this support is specifically for  @JsonProperty( stringLiteral ) . If there are other aspects to this annotation, please provide a documentation link and I'll b...

2.3.6.2 Issue 2798  - Summer '25 / API v64.0 update Updated the SOAP client for API v64.0. Updated the API version used for primary communication with Salesforce APIs to 64.0. Added 64.0 as an available API version number for configured connections. Updated  metadata.xsd  based on the API v64.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in Summer '25. Updated the bundled  completions?type=apex  Tooling REST API response to be based on the API v64.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '25 changes. Updated the bundled SLDS CSS and SVG icons to 2.27.1. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Added support for LWC local dev preview for a  single LWC component . This manifests as another context action,  Start local development server for...