2.4.1.4

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 install/configure the LSP4IJ plugin and download/register the language server respectively. IC still provides completions and references for Agent Script target references to Apex classes, Flows, etc., that aren't provided by the language server.
• It's now possible to cancel background operations that are making read-only Salesforce API calls immediately, e.g., during OST generation, metadata retrieval, SOQL/SOSL query execution, etc. Note that API calls that can make changes to the org, e.g., DML operations, anonymous Apex script executions, etc., cannot be canceled immediately unless the API supports explicit cancellation, e.g., deployment via the Metadata API. This is to prevent any confusion about org state if an org-mutating operation were to be canceled mid-call with the API continuing to execute in a detached mode.
• When Vitest reports branch expression ranges that don't match actual expressions exactly, IC adjusts to the largest expression in the reported range for display purposes.

2.4.1.3

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 original discussions there have unquestionably valuable contents.

2.4.1.2

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 historical purposes.
    • Original issue comments are now contained within the main issue details with information about the comment creator user ID (as text, not an actual user ID link), comment creation date/time, etc.
    • As much as possible, original images and attachments have been preserved in the migrated issues.
    • All migrated issues show as being opened by me as there was no good way to have them be opened by the original user ID, even mapped from Bitbucket to GitHub. Of course, any newly-opened issues will have the correct ownership.
    • Bitbucket issue components have been migrated to GitHub labels, and the new labels have a much more fine-grained and organized taxonomy.
    • Similarly, Bitbucket issue priorities have been migrated to GitHub labels of the form priority:<priority>. Newly-opened issues in GitHub will have a first-class priority.
    • I've added issue templates for bugs and feature requests/enhancements. I may add other templates based on observed needs. When opening new issues, please try to use the existing templates — or let me know that a new template is needed — and please try to provide the information requested by the respective template.
  • User guide - All user guide content has been migrated and refreshed, so it should reflect the current product state accurately in terms of content, screenshots, etc. I'm also planning to update my issue resolution process so that any change that has user guide impact results in a proper update to the user guide as part of the acceptance criteria. Finally, I'm planning to add new user guide topics for other features such as the Anonymous Apex/SOQL Query/SOSL Query/Log Analyzer tool windows, etc.
  • Discussions - Because GitHub has a very nice, first-class discussions feature, I'm planning to retire the Google disucssion groups in favor of it. The original discussion groups will remain in a read-only mode for historical/reference purposes, but all new discussions should occur in GitHub.
• I've also updated all external references to Bitbucket content — both issue links and user guide topics — to point to the respective new locations. This includes links in IC itself as well as those in the main IC Web site.
• Added convenient links to the Web Site, Terms and Conditions, Privacy Policy, User Guide, Issues, and Discussions in the Illuminated Cloud | Configure Application | About tab.
• Speaking of the IC Web site, this exercise has motivated me to refresh it as well, though that may not happen immediately. Given the value of the user guide refresh, I'm thinking the Web site is also long-overdue for some attention.

If you find any issues from this migrated content, please let me know so that I can correct them.