Illuminated Cloud Announcements

2.4.1.4 Issue 2979 - Implemented several performance improvements around the build options dialog and module subscription editor in projects with very large amounts of org metadata. Issue 2985 - Fixed several issues with metadata types that are either not reported properly by the Metadata API or have insufficient information about parent/child metadata type relationships. This addresses some specific issues, but I'm sure there are other metadata types — specifically those gated by feature flags — that are still unaddressed. I'll be happy to take care of those, but I'll need to know the specific metadata types and enabling feature flags. Issue 2990 - IC application-level settings now try to infer project-level context better when opened via system settings. Added support for the Agent Script Language Server for *.agent files. As usual, LSP4IJ is required, and you must also download the language server distribution and register it with IC. IC will, of course, help insta...

2.4.1.3 Issue 2987 - Fixed several issues with Flow diagrams in 2026.2. While diagrams now render properly, there are still a few remaining issues that seem attributable to the newer version of Mermaid used by the 2026.2+ version of the Mermaid plugin: Icons do not display properly, so they're not included in diagram nodes. The diagram look-and-feel options, e.g., Elk renderer and curve styles, don't seem to have any effect. Fixed several issues with copying Apex string literal contents to the system clipboard that were introduced with Apex multiline string support. A quick reminder that the public issue tracker , user guide , and discussions have been completely migrated from Bitbucket and Google Groups respectively into GitHub. The original public issue tracker and user guide will be removed by Atlassian on August 20, 2026 as part of its sunsetting of Bitbucket Cloud issues and wikis , and the original discussion groups are now read-only historical archives given that the o...

2.4.1.2 The migration of the public issue tracker and user guide from Bitbucket Cloud to Github is now complete. The original resources are now in a read-only mode and will no longer be available starting August 20, 2026. The new resources are: Issue tracker - All issues have been migrated with as much of the original content as possible. A few items of note: Some issue numbers have changed, so if you have external references to the originals, you may need to update those not just for Bitbucket vs GitHub, but also for the new issue numbers. The issue titles are (mostly) unchanged, so you should be able to locate the new one easily by title. I've updated all internal links between issues to accommodate for these changes. Unfortunately I wasn't able to attribute migrated issues to the GitHub user IDs corresponding to the original Bitbucket issue creator user IDs, but the original Bitbucket user IDs and creation date/time information are included in the migrated issues for histo...

2.4.1.1 Enabled support for the 2026.2 JetBrains IDEs that are now in a release candidate state. As always, if you see issues with a pre-release IDE build, please revert to the most recent released build and let me know about the issues you've seen so that I can address them. NOTE: I've pretty much completed the Bitbucket-to-GitHub migration for the public issue tracker and user guide/wiki. I'm planning to flip the switch early next week with all external references updated accordingly and the Bitbucket functionality switched to a read-only mode with links to the replacing features in GitHub. There will be a small IC2 release to accompany this change since some of the external references are in IC2 itself. 

2.4.1.0 Many improvements and fixes for Apex multiline strings and string templates: Generalized string template support so that it works properly for both simple strings and multiline strings. Added support for bidirectional navigation and highlighting of string template variable declarations and references. Note that highlighting of references when the caret is on a ${name} reference in a string literal is still not perfect. Unfortunately this seems to be due to some aggressive caching in the JetBrains IDE itself since the string literal is technically a single element, so I may not be able to improve it beyond its current state. Added support for renaming of string template variables via both the associated map key and any reference to that key. Changed multiline string literal syntax highlighting to match how the analogs are displayed in other first-class languages such as Java and JavaScript/TypeScript. Added indent guides to show the left border of indented multiline string cont...

2.4.0.9 Issue 2979 - Fixed an issue that could cause the derived invokable declaration index to fail indexing, resulting in constant "Analyzing" behavior. Added support for aer-based integration test execution with aer 1.2.0 +. Added support for Agent Script's subagent directive type including code completion, reference navigation, syntax highlighting, etc. Fixed an issue where class methods weren't being included in System.Label variant completions.

2.4.0.8 Issue 2974 - Summer '26 / API v67.0 update Updated the SOAP client for API v67.0. Updated the API version used for primary communication with Salesforce APIs to 67.0. Added 67.0 as an available API version number for configured connections. Updated metadata.xsd based on the API v67.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in Summer '26. Updated the bundled completions?type=apex Tooling REST API response to be based on the API v67.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '26 changes. Updated the bundled SLDS CSS and SVG icons to 2.30.4. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Usages of SOQL WITH SECURITY_ENFORCED in Apex source files with API version 67.0+ are now flagged as errors with a quick-fix to use WITH USER_MODE instead. Apex classes with...