Illuminated Cloud Announcements

2.3.7.5 Issue 2847  - Prospective fix for an issue observed in user-provided log extracts where IC is attempting to cache a namespace for an invalid, non-null element. This could well be a downstream side-effect of an another issue. If so, I'll continue to work with the reporting users to find and fix the ultimate root cause. Issue 2848  - Added a new tab-level option to the SOQL Query tool window to disable query validation specifically for that tab. This is useful when a query would be flagged by certain validations, e.g., as having unconstrained sub-queries, but the user knows that the query will execute without issue. It allows validation to be disabled for exactly those queries while remaining enabled in general. Validation can be enabled/disabled via a toolbar toggle button and via a checkbox in all of the actual validation dialogs. Issue 2849  - Added aggressive caching of node IDs in the build options dialog as a prospective fix for yet another "Illuminated Cloud ...

2.3.7.4 Issue 2815  (progress) - Added cross-metadata references for: Animation rules Apex test suites Custom applications Custom objects (improvements) Dashboards Flexipages Flows Object and field translations Page layouts (improvements) Path assistants Quick actions Territory2 rules Workflows Most of the references added above are for SObject type and field names, though a few are for other metadata types such as Apex classes referenced in Apex test suites. I'm keeping a running list of other types of cross-metadata references that could be added and will likely implement those as well, though perhaps not immediately. If you find other specific SObject type/field references that are not being added properly based on these changes, please feel free to log new bugs in the public issue tracker with examples and I'll be happy to address them. Issue 2835  - Migrated to newer plugin SDK APIs to determine the installed/enabled state of various third-party plugins that IC integrates...

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