Illuminated Cloud Announcements

2.3.7.3 Issue 2815  (progress) - Added more cross-metadata references for: SObject fields in custom metadata ( *.md[-meta.xml] ). SObject fields in reports ( *.report[-meta.xml] ). SObject types and fields in report types ( *.reportType[-meta.xml] ). apex:// ApexTypeName  references. I think the primary unaddressed metadata type at this point is Flow, so that will obviously be the next one that gets my attention. Improved usage type categorization to include these types of cross-metadata references properly. Fixed several issues with dynamic type inference for referenced LWC component types in JavaScript and TypeScript. Fixed an issue with LWC component names used in CSS selectors in LWC JavaScript and TypeScript, particularly for selectors and dynamic component creation. The Apex  Unused Declaration  inspection now properly considers references from XML metadata files other than  package.xml  and permission set/profile metadata. The former should be consid...

2.3.7.2 Issue 2815  (progress) - Added more cross-metadata references, specifically for those to non-decomposed child metadata in metadata format projects, e.g., custom fields in  *.object  files. As stated previously, I'll continue to chisel away at this gradually across upcoming builds until I feel I've covered what I can. Issue 2823  - IC now verifies that the module's configured default source root matches the specified default package directory in  sfdx-project.json  in modules/projects with multiple source roots. A module resolution fix is provided to update the default source root to match the default package directory if different. Issue 2827  - Fixed an issue where violations reported by Salesforce Code Analyzer in files without first-class language support could be incorrectly attributed at the file-level instead of at the reported location. Issue 2830  - Fixed an issue where the user could be prompted about deployment of unsubscribed me...

2.3.7.1 Issue 2719  - Implemented a few improvements around large Mermaid Flow diagrams that would previously have resulted in "Maximum text size in diagram exceeded" errors. Note that unfortunately it does not look like a full resolution to  this issue  will be coming in the foreseeable future, so I'm now focusing on improvements to help minimize the likelihood of it: Reduced the overall size of the generated Mermaid document by changing indentation from four spaces to one space. Obviously this isn't a huge win, but in larger documents it can empirically reduce the overall size by ~10% which can help some of those documents to squeeze under the 50K default threshold. Added a new Flow diagram config option for the functionality added for  issue 2800 ,  Inline text templates  (defaults to  enabled ), that can be disabled if inlined text templates are causing documents to exceed this threshold. Note that this option is for the entire Flow diagram feature...

2.3.7.0 Issue 2803  - Removed a potentially long-running read action when IC generates the contents of  .illuminatedCloud/lwc/types  that could be reported to the end user as "Illuminated Cloud might be slowing things down". Issue 2815  (partial) - Added more metadata cross-references, specifically for SObject fields referenced in other XML metadata files such as indexes, layouts, listview, validation rules, etc. I also expanded the behavior of references search for  *.field-meta.xml  files. Issue 2826  - Added sorting attributes to the  lightning-tree-grid  component. Fixed an issue where the  oncancel  attribute was missing for custom  LightningDataTable  implementations. Note that the latter change only affects commercial JetBrains IDEs due to how attributes are found via TypeScript inheritance relationships. Fixed a potential NPE when parsing Apex debug logs if log level highlighting is enabled and  Color Scheme |...

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