2.4.3.0 release notes

2.4.3.0

  • Discussion 3028 - Added installation and configuration support for the JetBrains Air plugin in Illuminated Cloud | Configure Application | Agentforce | Vibe Coding. Note that the Salesforce rules are added to the project's AGENTS.md file, so merge them carefully when installing them.
  • Issue 3036 - IC-specific stack trace filters are now applied only in the context of IC projects.
  • Issue 3037 - Added missing System.Label.get(namespace, label) signature. Added missing bundled API docs for System.Label. Note that OST regeneration is required to see the effects of the missing signature change.
  • IC now prompts to remove obsolete/orphaned sf-skills files after updating from the latest repo version. Note that you should only remove files that are known to be from an older version of the sf-skills repo and not custom skills files that you've added.
  • Added the missing addError(String msg[, Boolean escape]) methods to all primitive data types in OSTs generated using the Apex Symbol API for system types. Note that OST regeneration is required to see the effects of this change.
  • If the Apex Symbol API fails during OST generation, IC now degrades gracefully to the original APIs used for generation of the same subset (s) of the OST. The goal here is to allow the user to enable the Apex Symbol API for OST generation broadly even when it may fail against a specific org for a subset of types, most often database category types.
  • Improved presentation of test failures of the form Expected vs. Actual and Same value by rendering the labels in bold to distinguish them clearly from the actual values.
  • Significant internal refactoring/reorganization of IC's application-level settings. This should be 100% invisible to end users as settings are automatically migrated into the new structure. If you find that application-level settings are incorrect after this update, please let me know.
  • Addressed several reported long read actions and other types of pauses. There are still several others that I plan to address based on reported instances, but they will require a bit more time.