Illuminated Cloud Announcements

2.3.6.9 Issue 2815  (partial) - This is the first set of enhancements for what will be a series of changes to add proper cross-file references to Salesforce metadata more consistently. This one adds references in  package.xml  files and permission set/profile XML files for all explicitly referenced metadata. If you find that there are still missing references in these files, please let me know so that I can address them. If you're interested in what other references are slated to be addressed, please follow comments and updates on the issue linked above. Issue 2822  - Addressed several issues with LWC TypeScript support in metadata format projects: JavaScript files that are output from TypeScript generation are refreshed in VFS to ensure that the IDE gets up-to-date documents for inclusion in the deployment archive. LWC TypeScript source files are no longer included in the deployment archive. IC no longer gets confused about the connection type due to the presence of...

2.3.6.8 Updated IC for JetBrains' 2025.2 releases now that they've entered a release candidate state. As noted previously, due to breaking plugin SDK changes in 2025.2, I've had to drop IC support for 2024.*, so please make sure that you're using 2025.1 or higher. Also, due to a wholesale change to one JavaScript API, some specific types of code completions are now only available in 2025.2, particularly those for the  config  parameter of the LWC  @wire  adapter. This change only affects those using IC with commercial JetBrains IDEs. Issue 2817  - Added support for the  LightningTypeBundle  metadata type. This is another pseudo-bundle metadata type that requires specialized handling. Note that deployment errors reported against files from these bundles do not specify a valid file, so IC currently follows the Salesforce CLI's precedent of attributing those errors to the bundle's  schema.json  file. Unfortunately this is rarely the actual file ...

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