[{"id":1195237,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1195237","version":"2.4.2.8","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1792086617000","file":"10253/1195237/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.2.8
\n Reissue of 2.4.2.7 with hotfix for Metadata Visualizer not showing visualizations in older IDE versions.\n \n - Issue 3026 - Added support for the Salesforce Metadata Visualizer to show in-IDE previews of supported metadata types, currently Agent Script scripts, flexipages, flows, permission sets, and SObject type definitions.\n
\n - This feature is disabled by default and can be enabled on a per-metadata type basis in Illuminated Cloud | Configure Application | Other | Enable Metadata Visualizer for.
\n - The Metadata Visualizer only supports source format metadata files, so this feature is only available in source format projects.
\n - The Metadata Visualizer option for Flow files is mutually-exclusive with the Use preview editor for Flow files option. At most one of these options can be enabled for Flow files.
\n - IC must find the Node.js executable —
node on Mac/Linux or node.exe on Windows — in the system execution path for this feature to be enabled. \n - If Metadata Visualizer is enabled for a file's type and the Node.js executable is found, a file-level annotation will be displayed to help install Metadata Visualizer for the project.
\n - Once installed, the IDE's standard text-editor-with-preview will be used for enabled metadata file types with the metadata file displayed on the left-hand side and the visualization displayed on the right-hand side. You can, of course, toggle between the split view, the metadata file, or the visualization.
\n - Visualizations update automatically when associated metadata files have been modified and saved to disk. Unsaved changes are not reflected in the visualization.
\n - IC's integration of Metadata Visualizer is read-only. Visualization features that offer to change metadata file contents, e.g., the Select to Edit and Select buttons, are not active at present. I will investigate whether it's possible to handle those features in this integration.
\n
\n - Issue 3032 - Partially fixed an issue that could result in an HTTP 403 with error message
INVALID_INPUT: runTestsAsynchronous rejects an empty testMethods array during execution of Apex test classes with a large number of test methods. Previously the asynchronous Apex unit test execution API would fail with an HTTP 500 / Internal Server Error if the request included a test class containing 150+ test methods. IC included a workaround to execute the entire test class when this situation is detected, but in Winter '27 / API v68.0, such a request now results in the aforementioned HTTP 403. The good news is that the original HTTP 500 error that motivated this workaround seems to have been partially resolved, so I've removed the workaround. I've said \"partially\" twice now because I did observe a few examples of the same HTTP 500 failure in test classes with very large numbers of test methods, and I've provided examples of concrete reproductions to the appropriate folks at Salesforce so that the root cause bug can be resolved properly. \n - Fixed an issue that could result in stale project information being used after a project has been closed and reopened.
\n
\n \n","since":"253.33813.25","until":"262.*","sinceUntil":"253.33813.25 — 262.*","channel":"","size":32890121,"downloads":222,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.3.6 — 2026.2.3","RUBYMINE":"2025.3.6 — 2026.2.3","PYCHARM":"2025.3.6 — 2026.2.3","PYCHARM_COMMUNITY":"build 253.33813.25 — 262.*","WEBSTORM":"2025.3.6 — 2026.2.3","IDEA_COMMUNITY":"build 253.33813.25 — 262.*","IDEA":"2025.3.6 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1192443,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1192443","version":"2.4.2.6","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1791823104000","file":"10253/1192443/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.2.6
\n \n - Issue 3007 - Winter '27 / API v68.0 update\n
\n - Updated the SOAP client for API v68.0.
\n - Updated the API version used for primary communication with Salesforce APIs to 68.0.
\n - Added 68.0 as an available API version number for configured connections.
\n - Updated
metadata.xsd based on the API v68.0 Metadata API SOAP WSDL. \n - Updated the OST version number to prompt regeneration for system API changes in Winter '27.
\n - Updated the bundled
completions?type=apex Tooling REST API response to be based on the API v68.0 REST endpoint. See below for more information about support for the new Apex Symbol API. \n - Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Winter '27 changes.
\n - Updated the bundled SLDS CSS and SVG icons to 2.264.1.
\n - Updated for new org features, standard value set names, metadata XML file type extensions, etc.
\n - Updated all integrated API documentation.
\n - Added support for the new Apex Symbol API when generating project offline symbol tables.\n
\n - This feature is currently in beta, so it is disabled by default.
\n - This integration includes new configuration options in Illuminated Cloud | Configure Application | Other | Offline symbol table generation for whether or not to use the Apex Symbol API during OST generation:\n
\n - System types - When unchecked (default), the Tooling API's
completions?type=apex REST resource is used, though its output has been refined significantly based on the Apex Symbol API response. When checked, the Apex Symbol API's builtin category is queried, though its response is also refined based on observed issues and inconsistencies, all of which have been reported to Salesforce. The Apex Symbol API includes more information about annotations and modifiers, property accessors, and even ApexDoc-style documentation. It's also significantly faster than the Tooling API's completions?type=apex REST resource, so enabling this option can often improve OST generation times significantly.\n \n - Use bundled system type documentation - When checked, the bundled documentation for system types is used instead of the API-reported documentation. The bundled documentation for system types can often be more complete — both content and formatting — than the API-reported documentation. Disabled by default.
\n
\n - Custom types - When unchecked (default), custom Apex types from installed packages and other types that don't exist locally in the project are queried using the Partner and Tooling APIs. When checked, the Apex Symbol API's
database category is queried. Note that I have observed a number of issues with this specific category where valid types are not included in the response due to compilation issues and even internal server errors. \n - Dynamic types - When unchecked (default), the
DataWeaveScriptResource type's inner classes are populated based on the local project's *.dwl files, and classes in the ExternalService namespace are populated based the corresponding entries in the Salesforce Setup UI's Custom Code | Apex Classes | Dynamic Apex Classes section. When checked, the Apex Symbol API's dynamic category is queried for population of these types which includes everything in that same Dynamic Apex Classes section. Note that DataWeaveScriptResource inner type names now reflect the associated script names exactly and are no longer capitalized. \n
\n - My recommendation: At present, I recommend enabling only System types and Dynamic types because of the errors I've seen with Custom types. If doing so results in missing or invalid OST entries, please disable them and report the specific issues to me so that I can work with Salesforce to resolve them. As these issues are addressed by Salesforce, I will update my recommendation, and ultimately I hope to enable the Apex Symbol API as the default setting and eventually remove support for the replaced APIs.
\n
\n - Added a Show Web Console... action to the Illuminated Cloud context menu that opens the new Web Console in the project's associated organization. The Web Console must, of course, be enabled in the org, and IC must first open another org page, specifically the Web Console Settings page, to ensure an active browser session before opening Web Console in a second tab. If you see
Page doesn't exist in the resulting Web Console tab, please enable the feature in the Web Console Settings tab. I will continue to investigate ways to avoid having to open an additional tab if possible. \n - Added an Apex API version code inspection that flags Apex source files with an API version under 9.0 as invalid (errors), and those and in the range 9.0–19.0 as being scheduled for retirement (warnings), both with a quick fix to update the API version based on the project configuration.
\n - Apex compiler warnings reported during deployment are now displayed in a notification.
\n - Added support for the
@BeforeClass annotation for Apex integration tests including support for generating @BeforeClass methods in integration test classes that do not current include them. \n - Added full support for the SOQL
SET OPTIONS clause. \n
\n
\n \n","since":"253.33813.25","until":"262.*","sinceUntil":"253.33813.25 — 262.*","channel":"","size":32857624,"downloads":2009,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.3.6 — 2026.2.3","RUBYMINE":"2025.3.6 — 2026.2.3","PYCHARM":"2025.3.6 — 2026.2.3","PYCHARM_COMMUNITY":"build 253.33813.25 — 262.*","WEBSTORM":"2025.3.6 — 2026.2.3","IDEA_COMMUNITY":"build 253.33813.25 — 262.*","IDEA":"2025.3.6 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1189818,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1189818","version":"2.4.2.5","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1791475885000","file":"10253/1189818/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.2.5
\n \n - Issue 3029 - Fixed an issue with aer-based Apex debugging where the aer DAP server wasn't being started with the correct working directory. The fix is not in IC, though, and is instead an accepted and merged pull request against the corresponding LSP4IJ bug. Once that new build is available, it should resolve the associated issues with relative paths and finding
.aerrc. \n - Fixed an issue with the Apex recursive call line marker provider incorrectly adding line markers for calls to the same method on other instances.
\n - Fixed issues with quick-fixes that use templates in batch inspection runs. Those with complex templates are no longer available in batch mode. Those that require selection of a single value from a common list of values now prompt for that value once and apply the quick-fix to all selected instances, e.g., the sharing mode modifier that should be added to all selected classes without a sharing mode.
\n
\n \n","since":"253.33813.25","until":"262.*","sinceUntil":"253.33813.25 — 262.*","channel":"","size":32518344,"downloads":1834,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.3.6 — 2026.2.3","RUBYMINE":"2025.3.6 — 2026.2.3","PYCHARM":"2025.3.6 — 2026.2.3","PYCHARM_COMMUNITY":"build 253.33813.25 — 262.*","WEBSTORM":"2025.3.6 — 2026.2.3","IDEA_COMMUNITY":"build 253.33813.25 — 262.*","IDEA":"2025.3.6 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1185439,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1185439","version":"2.4.2.4","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1790870207000","file":"10253/1185439/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.2.4
\n \n - Issue 2980 - IC now displays the project's
.aerrc file contents, if present, in the Apex test run configuration editor so that it's obvious exactly what command-line options will be used when executing Apex tests via aer. It's still possible to configure additional aer command-line options on a per-run config basis in the run configuration editor as well. \n - Issue 2924 - Added a new deployment Apex test level,
RunDependentTests, that is conceptually similar to RunRelevantTests, but the set of tests to be executed is computed by IC before deployment — and then executed using the RunSpecifiedTests test level — instead of being computed by the Salesforce server.\n \n - There are notable differences in how IC computes transitive dependents vs. how Salesforce computes them (at least at present):\n
\n - IC specifically computes dependent relationships with member-level granularity whereas Salesforce computes them with class-level granularity. This means that if an intermediate dependent member is found, IC will only include transitive dependents of that member whereas Salesforce will include transitive dependents of the entire containing top-level class. This can result in
RunRelevantTests executing more tests than RunDependentTests, with the extras generally being unnecessary to validate the original context. \n - IC's transitive dependent calculator takes into account both direct relationships expressed via Apex references and indirect relationships expressed in other metadata types that use Apex, e.g., flows and presentation tier frameworks. This can result in
RunDependentTests including tests that are not found by RunRelevantTests. \n - Salesforce will only execute dependent tests for deployment payload members that are modified relative to the server. IC will execute all dependent tests even if nothing has been modified relative to the server. This means that
RunRelevantTests is significantly more efficient than RunDependentTests when deploying large payloads where only a small subset of the payload members have actually changed. \n
\n - IC's transitive dependent calculator takes into account
@IsTest(critical=true) and @IsTest(testFor=...) annotations, so existing explicit test dependency relationships are properly respected. \n - If you use this new test level and find any issues with missing/incorrect dependents, test execution failures specific to this new test level, etc., please let me know and I'll take care of them.
\n
\n - Issue 3010 - IC includes a new Apex code inspection, Access mode validation, that evaluates Apex non-test classes for correct and safe sharing mode and access mode usage.\n
\n - This new inspection is enabled by default and included in the bundled inspection profiles, but if you have an existing inspection profile with Disable new inspections by default enabled, you will need to add it to that inspection profile explicitly.
\n - The inspection includes the following configuration options:\n
\n - Check API v67.0+ files only - When enabled, the inspection only applies to Apex classes and triggers with API v67.0 or higher. Enabled by default given the default sharing and access mode behavioral changes introduced in that API version.
\n - Check database operations in classes without a sharing mode - When enabled, classes without a sharing mode that perform database operations are reported. Enabled by default.
\n - Check system mode database operations in classes without a sharing mode - When enabled, system mode database operations in classes without a sharing mode are reported. Disabled by default.
\n - Check user mode database operations in classes without a sharing mode - When enabled, user mode database operations in classes without a sharing mode are reported. Disabled by default.
\n - Check static database operations without an acccess mode - When enabled, static database operations without an access mode are reported. Disabled by default.
\n - Check dynamic database operations without an acccess mode - When enabled, dynamic database operations without an
AccessLevel invocation argument are reported. Disabled by default. \n
\n - As always, if you find false positives or negatives reported by this new inspection, or if you have ideas for how it can be improved, please let me know about them, ideally with concrete examples of issues or omissions.
\n
\n - Apex dependents-based test run configurations now include all
@IsTest(critical=true)-annotated unit tests in addition to those found via dependents analysis. \n - Significantly improved the way that unit test results are displayed in the correponding Messages tabs when tests are executed as part of deployment. Now test successes and failures are displayed in their own respective sections distinct from deployment successes and failures, and all test results are hyperlinked to the respective source code, either the test method that was executed successfully or the specific line/column for which a test failure was reported.
\n - Added full support for Angular UI bundle templates. Note that unlike React, Angular support requires a commercial JetBrains IDE license.
\n - Added missing project templates when creating source format projects, specifically
agent, angularexternalapp, angularinternalapp, reactexternalapp, and reactinternalapp. \n - Fixed an LWC TypeScript compiler error that could occur when using TypeScript 7+. I recommend using TypeScript 6 due to other potential breaking changes in TypeScript 7, specifically with ESLint, but this should at least ensure that the TypeScript 7 compiler is found and used by the IDE when compiling LWC TypeScript source files.
\n - Updated the default/recommended case for Apex annotation attributes to be Camel case, leading lower instead of Camel case, leading upper. Quite frankly, I made a mistake on that specific default originally, and this change is long overdue. Annotations are analogous to classes, and their attributes are analogous to those class' fields. As a result, annotation names should follow
ClassName case conventions, and their attributes should follow fieldName case conventions. I've gone back and forth on this particular decision because it changes the default Apex formatter behavior for existing users, but in the end I prefer that the default be correct based on the aforementioned case conventions. If you wish to retain the previous case convention for annotation attributes, e.g., to minimize a potentially noisy (ideally one-time) change to your existing code base, simply change Settings | Editor | Code Style | Apex | Case | Apex | Annotation attribute from Recommended to Camel case, leading upper. \n
\n \n","since":"253.33813.25","until":"262.*","sinceUntil":"253.33813.25 — 262.*","channel":"","size":32512891,"downloads":2414,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.3.6 — 2026.2.3","RUBYMINE":"2025.3.6 — 2026.2.3","PYCHARM":"2025.3.6 — 2026.2.3","PYCHARM_COMMUNITY":"build 253.33813.25 — 262.*","WEBSTORM":"2025.3.6 — 2026.2.3","IDEA_COMMUNITY":"build 253.33813.25 — 262.*","IDEA":"2025.3.6 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1178722,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1178722","version":"2.4.2.3","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1790265293000","file":"10253/1178722/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.2.3
\n \n - Issue 2885 - Added support for additional decomposed metadata types. As with the underlying feature, this support is beta. If you encounter issues with it, consider disabling optional decomposition and please report those issues to Salesforce or IC as appropriate.
\n - Issue 2936 - Added support for both types of
edition values in project-scratch-def.json files. Values are still written in the documented form when scratch org definition files are written by IC. \n - When Apex Execution Runtime (aer) is used for Apex code coverage, IC now uses the covered line information instead of computing its own set of executable lines.
\n - The tooltip for the Salesforce skills Update button in the Agentforce configuration tab now includes details about the nature of the recommended update, e.g., the installed and available version date/time stamps.
\n - Improved the offline symbol table generator's support for
ExternalServiceRegistration classes which can sometimes yield HTTP 500/Internal Server Error responses but then succeed on retry for the exact same class. \n - Numerous related fixes and improvements, particularly around generalized metadata decomposition handling.
\n
\n \n","since":"253.33813.25","until":"262.*","sinceUntil":"253.33813.25 — 262.*","channel":"","size":32477661,"downloads":2509,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.3.6 — 2026.2.3","RUBYMINE":"2025.3.6 — 2026.2.3","PYCHARM":"2025.3.6 — 2026.2.3","PYCHARM_COMMUNITY":"build 253.33813.25 — 262.*","WEBSTORM":"2025.3.6 — 2026.2.3","IDEA_COMMUNITY":"build 253.33813.25 — 262.*","IDEA":"2025.3.6 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1173652,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1173652","version":"2.4.2.2","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1789663085000","file":"10253/1173652/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.2.2
\n \n - Issue 3011 - Prospective fix for an IDE freeze during initial dynamic file type determination.
\n - The Apex Unresolvable Reference code inspection now verifies property accessor visibility based on the reference context with write expressions being checked against the property setter and read expressions being checked against the property getter. This becomes particularly useful in Winter '27 where the Apex Symbol API includes property getter and setter visibility information for properties of system types.
\n - The Apex Annotation and Modifier Agreement code inspection now flags property accessors with higher visibility than their containing properties as errors with quick fixes to adjust the property or property accessor visibility to a valid value relative to the other.
\n
\n \n","since":"253.33813.25","until":"262.*","sinceUntil":"253.33813.25 — 262.*","channel":"","size":32470951,"downloads":2630,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.3.6 — 2026.2.3","RUBYMINE":"2025.3.6 — 2026.2.3","PYCHARM":"2025.3.6 — 2026.2.3","PYCHARM_COMMUNITY":"build 253.33813.25 — 262.*","WEBSTORM":"2025.3.6 — 2026.2.3","IDEA_COMMUNITY":"build 253.33813.25 — 262.*","IDEA":"2025.3.6 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1167355,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1167355","version":"2.4.2.1","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1789056158000","file":"10253/1167355/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.2.1
\n \n - Removed support for JetBrains 2025.2 IDEs. Please make sure that you're using 2025.3+ (ideally the latest-and-greatest which is currently 2026.2.2) for continued IC plugin updates.
\n - Issue 3019 - Fixed a problem with commas in ApexDoc
@see description text being interpreted incorrectly as a comma-delimited list of targets. \n - Issue 3020 - Fixed a potential deadlock calculating the server time offset during the first Deploy Modified Metadata action against a specific connection after starting the IDE.
\n - Added support for per-test code coverage in aer. This is accessed using the IDE's standard per-test coverage feature. Note that you must be using aer 1.4+, and you must explicitly enable the feature in Illuminated Cloud | Configure Application | Apex | Apex Execution Runtime (aer) | Enable coverage by test.
\n - Integrated broad improvements in the OST's Apex system types based on the upcoming Apex Symbol API. In this version, IC does not yet use that API — it will be offered as an option when Winter '27 is GA — but this provides many of the fidelity benefits of that API that have not been available in the Tooling API's
completions?type=apex REST resource. To see the effects of this change, you must regenerate your OST. \n - Fixed an issue that could result in a newly-generated OST being perceived as invalid by the IDE because of concurrent read access to update
.illuminatedCloud/lwc/types while still writing the OST archive. \n - Fixed an issue showing SOQL Query tool window results when conversion of scientific values is enabled.
\n
\n \n","since":"253.33813.25","until":"262.*","sinceUntil":"253.33813.25 — 262.*","channel":"","size":32470530,"downloads":2572,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.3.6 — 2026.2.3","RUBYMINE":"2025.3.6 — 2026.2.3","PYCHARM":"2025.3.6 — 2026.2.3","PYCHARM_COMMUNITY":"build 253.33813.25 — 262.*","WEBSTORM":"2025.3.6 — 2026.2.3","IDEA_COMMUNITY":"build 253.33813.25 — 262.*","IDEA":"2025.3.6 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1160957,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1160957","version":"2.4.2.0","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1788453906000","file":"10253/1160957/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.2.0
\n This is a quick hotfix for a regression introduced in 2.4.1.9. I've primarily been working closely with Salesforce to validate the upcoming Apex Symbol API as a way to improve the fidelity and performance of IC's OST generation.\n \n - Issue 3018 - Fixed a regression where Compare With Server on a single file would result in multiple diffs being shown including the selected file and the intermediate temporary directories.
\n
\n Note that support for 2025.2 JetBrains IDEs will be removed soon, likely in next week's build. Please make sure that you're using 2025.3+ for the best experience going forward.\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32327395,"downloads":3001,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1154474,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1154474","version":"2.4.1.9","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1787846367000","file":"10253/1154474/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.1.9
\n \n - Issue 2983 - When rerunning individual test classes or methods from the test results tool window, the test execution engine that produces those results, either Salesforce org or aer, is used to filter the available test execution actions. Note that the IDE's default test executor cannot be filtered and is always offered, but if selected within a short time after showing the context menu for a test class or method in the test results view, the test execution engine for that view will be used.
\n - Issue 3008 - If a metadata retrieval is requested for immediate population of project files (as opposed to retrieve-for-merge or compare-with-server) and its payload includes files that were not explicitly part of the original request, also exist locally in the project, and are different from their local counterparts, the user is now notified and retrieve-for-merge behavior is used to allow careful reconcilation of these unrequested changes.
\n - Issue 3012 - Improved the previously-stubbed interfaces for the LWC state management APIs. The documentation for these isn't great, at least in terms of the exact interfaces, but hopefully what I've provided here is quite decent. I'm certainly open to suggestions for improvement and of course fixes if there are still issues or inaccuracies.
\n - Issue 3013 - Added a few missing properties in the LWC record API module types.
\n - Issue 3014 - Fixed an issue with LWC TypeScript files that import HTML and CSS files.
\n - Fixed a few issues with Flow diagrams in 2026.2+/Mermaid 11+:\n
\n - Restored diagram node icons.
\n - Removed the diagram configuration option to use the Elk renderer since it doesn't seem to be supported (or at least have any effect) in Mermaid 11+.
\n
\n - Improved UI bundle creation error handling and reporting.
\n - Improved the way that IC helps install the plugin update when a new version is detected. Previously when a new version was found, the Settings | Plugins dialog would be displayed focused on the IC2 plugin. However, it looks like there's no guarantee that the IDE will have updated its plugin repository version information by the time that dialog is displayed, so IC now explicitly triggers the IDE's Check for Updates action to force an update notification (assuming that the local machine allows the IDE to communicate with the JetBrains plugin repository).
\n - Many other internal improvements to strengthen the foundation for subsequent work. I've tested these changes extensively, but if you do find any issues or regressions, please let me know and I'll address them ASAP.
\n
\n Note that support for 2025.2 JetBrains IDEs will be removed soon. Please make sure that you're using 2025.3+ for the best experience going forward.\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32328182,"downloads":2682,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1137962,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1137962","version":"2.4.1.8","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1786635788000","file":"10253/1137962/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.1.8
\n \n - Issue 2957 - Fixed an issue where errors could occur when adding/removing Apex offline debugger server-side checkpoints.
\n - Issue 3002 - Fixed an issue with
@NamespaceAccessible symbols from installed managed packages with the same namespace as the org not being properly rendered into the OST. Note that you must regenerate your OST to see the effect of this fix. \n - Issue 3003 - Fixed an issue where file copy/paste-for-overwrite in the IDE could result in IC prompting to remove the corresponding metadata files from the subscription and org. This is because the IDE actually does remove the original files and create new replacement files. IC now ignores the file removal events in this specific scenario.
\n - Issue 3004 - By default large numeric values are returned by the SOQL and SOSL query APIs in scientific notation, and the SOQL Query and SOSL Query tool windows simply show the returned data. Now those tool windows include a configuration option, Convert scientific notation values (disabled by default), that will convert these into their raw value counterparts for display and export. Note that this configuration option is actually shared between the two tool windows, so enabling/disabling it in one will do so in the other as well.
\n - Issue 3005 - Improved error handling and reporting if IC fails to clone the Salesforce Skills GitHub repo. Now the exact
git clone command execution is written to the Messages tool window. In the case of the linked issue, the root cause was due to \"Filename too long\" errors from Git on Windows. \n - Fixed an issue with the LSP4IJ DAP-based aer debugger not stopping on breakpoints properly.
\n - Added concrete priorities to the Apex line breakpoint types — local breakpoint, server checkpoint, and
aer DAP breakpoint in that priority order — for consistent and reliable behavior when adding line breakpoints. I've also asked JetBrains if it's possible to prompt the user for the desired breakpoint type when adding a line breakpoint instead of always adding the highest priority breakpoint. Pending their response, I'll see if I can improve the experience when adding line breakpoints a bit more. \n
\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32221145,"downloads":3189,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1128263,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1128263","version":"2.4.1.7","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1786030874000","file":"10253/1128263/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.1.7
\n \n - Issue 2998 - IC no longer bundles the Salesforce skills. Instead it uses the GitHub repo for Salesforce skills, checking the latest published version against the installed version and, if not yet installed locally or an update is available, cloning the repo into a temp directory and installing those. Note that there are significant differences between the original skills bundled with IC and the latest from that repo, so you might want to remove the existing skills before installing the new ones. Of course, if you've customized those skills and/or added your own, you should reconcile carefully to avoid losing anything.
\n - When a project is opened — including as part of IDE startup — IC checks for a plugin update. While the IDE already does this for all installed plugins, it only looks for updates that are compatible with the installed JetBrains IDE. Given that IC maintains compatibility with (roughly) one year's worth of JetBrains versions, currently 2025.2-2026.2, users on older IDE versions would not be notified of IC plugin updates by the IDE itself once IC no longer supports those older IDE versions. This will help ensure that users are properly notified of updates and when they need to update the underlying IDE to install them.
\n - Fixed several issues with IC's extensions to the IDE's HTTP Client tool:\n
\n - In unlicensed IDEs with the HTTP Client plugin installed and enabled (but effectively disabled), IC no longer offers the Salesforce API Request template.
\n - In all IDEs, IC only refreshes the access token if the request is specifically for a Salesforce API URL.
\n
\n
\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32220660,"downloads":2495,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1122324,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1122324","version":"2.4.1.6","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1785525021000","file":"10253/1122324/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.1.6 - Hotfix for 2.4.1.5
\n \n - Issue 3001 - For some reason the compiler marked the
catch block for UnexpectedErrorFault as invalid in IC's expired/invalid session handling logic, so I removed it. Sure enough, though, that exception still occurs, and now IC wasn't handling and recovering from it properly any longer. This is a targeted hotfix to restore that handling, albeit in a manner that the compiler no longer flags. \n
\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32713370,"downloads":2213,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1120201,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1120201","version":"2.4.1.5","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1785424725000","file":"10253/1120201/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.1.5
\n \n - Issue 2995 - Fixed several issues with ApexDoc Markdown processing during parsing, conversion to HTML, and formatting. Note that the ApexDoc formatter option to add HTML paragraph break elements on blank lines is now automatically disabled if any of the ApexDoc Markdown-related formatter options are enabled. Paragraph breaks are, of course, added in Markdown with two consecutive blank lines, so it didn't make sense to have both options enabled simultaneously.
\n - Improved the background threading behavior changes introduced in the previous build to allow immediate cancelation of read-only API calls. This specifically improves the \"hand-off\" of progress indicators across background threads, and eliminates (or at least minimizes) unnecessary creation of background/worker threads from existing background/worker threads.
\n - Added XSD element definitions for
FeatureParameter* and GenAiPromptTemplate metadata. \n - Improved progress indicator feedback when refreshing the org metadata cache.
\n
\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32713452,"downloads":1142,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1115037,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1115037","version":"2.4.1.4","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1784836017000","file":"10253/1115037/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.1.4
\n \n - Issue 2979 - Implemented several performance improvements around the build options dialog and module subscription editor in projects with very large amounts of org metadata.
\n - 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.
\n - Issue 2990 - IC application-level settings now try to infer project-level context better when opened via system settings.
\n - 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. \n - 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.
\n - 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.
\n
\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32709706,"downloads":2610,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1110256,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1110256","version":"2.4.1.3","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1784303888000","file":"10253/1110256/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.1.3
\n \n - 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:\n
\n - Icons do not display properly, so they're not included in diagram nodes.
\n - The diagram look-and-feel options, e.g., Elk renderer and curve styles, don't seem to have any effect.
\n
\n - Fixed several issues with copying Apex string literal contents to the system clipboard that were introduced with Apex multiline string support.
\n
\n 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.\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32723760,"downloads":2388,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1107371,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1107371","version":"2.4.1.2","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1784044830000","file":"10253/1107371/IlluminatedCloud2.zip","notes":"\n \n \n 2.4.1.2
\n \n - 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:\n
\n - Issue tracker - All issues have been migrated with as much of the original content as possible. A few items of note:\n
\n - 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.
\n - 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, etc.
\n - As much as possible, original images and attachments have been preserved in the migrated issues.
\n - 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.
\n - Bitbucket issue components have been migrated to GitHub labels, and the new labels have a much more fine-grained and organized taxonomy.
\n - 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.
\n
\n - 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.
\n - 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.
\n
\n - 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.
\n - 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.
\n
\n If you find any issues from this migrated content, please let me know so that I can correct them.\n \n","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32720459,"downloads":1999,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1104073,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1104073","version":"2.4.1.1","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1783697231000","file":"10253/1104073/IlluminatedCloud2.zip","notes":"\n 2.4.1.1
\n \n - Enabled support for the 2026.2 JetBrains IDEs that are now in a\n release candidate\n state. As always, if you see issues with a pre-release IDE build, please revert to the most recent\n released build and let me know about the issues you've seen so that I can address them.\n
\n
\n \n NOTE: I've pretty much completed the Bitbucket-to-GitHub migration for the public issue tracker and\n user guide/wiki. I'm planning to flip the switch early next week with all external references updated\n accordingly and the Bitbucket functionality switched to a read-only mode with links to the replacing\n features in GitHub. There will be a small IC2 release to accompany this change since some of the external\n references are in IC2 itself.\n
\n ","since":"252.28539.33","until":"262.*","sinceUntil":"252.28539.33 — 262.*","channel":"","size":32711525,"downloads":1449,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.2.3","RUBYMINE":"2025.2.6.1 — 2026.2.3","PYCHARM":"2025.2.6.1 — 2026.2.3","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.2.3","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.3"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1099611,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1099611","version":"2.4.1.0","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1783354806000","file":"10253/1099611/IlluminatedCloud2.zip","notes":"\n 2.4.1.0
\n \n - Many improvements and fixes for Apex multiline strings and string templates:\n
\n - Generalized string template support so that it works properly for both simple strings and\n multiline strings.\n
\n - Added support for bidirectional navigation and highlighting of string template variable\n declarations and references. Note that highlighting of references when the caret is on a\n
${name} reference in a string literal is still not perfect. Unfortunately this\n seems to be due to some aggressive caching in the JetBrains IDE itself since the string literal\n is technically a single element, so I may not be able to improve it beyond its current state.\n \n - Added support for renaming of string template variables via both the associated map key and\n any reference to that key.\n
\n - Changed multiline string literal syntax highlighting to match how the analogs are displayed in\n other first-class languages such as Java and JavaScript/TypeScript. Added indent guides to show\n the left border of indented multiline string contents.\n
\n - Fixed several issues with multiline string formatting.
\n - Whitespace-only lines in multiline string literals are no longer removed by the IDE on save and\n are padded as appropriate on format.\n
\n - The IDE's Join Lines action now works properly with multiline strings, joining with LF\n (
\\n) characters and ultimately into a simple single-line string when the last two\n lines in the multiline string are joined.\n \n - Add a new code inspection and quick-fix to convert simple string literals and string\n concatenation expressions into the associated multiline strings including automatic creation of\n the string template variable map if necessary. There are several restrictions and limitations on\n when/how this functionality is available:\n
\n - Multiline strings are only valid in API v67.0+. When converting a simple string literal\n or string concatenation expression to a multiline string in a file with an insufficient\n API version, IC automatically updates the Apex source file API version to the\n project/connection API version if at least 67.0 or the most recent platform API version\n — currently 67.0 — if not.\n
\n - Currently multiline strings are only valid in Apex source files with
LF\n (\\n) line separators. When converting a simple string literal or string\n concatenation expression to a multiline string, IC automatically converts containing\n files' line endings accordingly if needed. IC also includes a separate inspection for\n detecting Apex source files containing multiline strings and non-LF line separators and\n a quick-fix to change those files' line separators to LF.\n \n - The inspection is only enabled for simple string literals and string concatenation\n expressions that begin with a simple string literal and contain no multiline string\n literals.\n
\n - By default, the inspection is only enabled for simple string literals and string\n concatenation expressions that contain one or more newline (
\\n) characters,\n and the resulting multiline string is split based on those newlines resulting in the\n exact same contents. These two options can be enabled and disabled as desired.\n The inspection also includes an option to enable it for string concatenation expressions\n that do not contain any newlines but do span multiple lines. When this option is\n enabled and used, the resulting multiline string is split based on the editor line\n breaks found in the original string concatenation expression. Note that this\n changes the contents of the resulting string, but in many cases it does so\n according to the author's original intention. This option is disabled by default\n and must be enabled explicitly. The results of a multiline string conversion based on\n inferred line breaks should be reviewed carefully.\n \n
\n As noted previously, the quick-fix automatically converts all non-string literal expressions\n found in string concatenation expressions into string template variables. These variables are\n named based on the original expressions using what I hope are quite expressive and\n representative names, but if you find that some expressions are yielding incorrect and/or\n invalid variable names, please provide concrete examples so that I can improve them. As noted\n above, you can also use the IDE's Rename refactoring to rename string template variables\n and their usages easily. This inspection can be executed en masse to convert all supported\n string literals and concatenation expressions into the respective multiline strings using the\n IDE's Run Inspection by Name... action.\n \n
\n \n - Added support for the SOQL
FORMULA() function. Note that this is not currently enabled in\n any of my orgs so I haven't been able to confirm successful deployment, but the grammar has been updated\n to include support, and IC provides code completions, reference resolution, syntax highlighting, etc.,\n for both the SOQL function and the formula expression contents.\n \n - Fixed an accidental hard runtime dependency on LSP4IJ.
\n - Fixed an issue with SLDS Validator due to potential mismatched installed versions of LSP4J.
\n
\n \n NOTE: I'm planning to spend the next week or two finally migrating the public issue tracker and user\n guide / wiki from Bitbucket Cloud into GitHub (including a long overdue refresh of the user guide content).\n As a result, there will be a slight pause on planned IC2 releases during this migration. Of course, if\n anything critical needs to be addressed during this time, I'll take care of it, and as soon as the migration\n is complete, I'll post links for the new resources. I'll then return to the standard (approximately) weekly\n IC2 release cadence.\n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":32711849,"downloads":2090,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.1.5","RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1087419,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1087419","version":"2.4.0.9","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1782413479000","file":"10253/1087419/IlluminatedCloud2.zip","notes":"\n 2.4.0.9
\n \n - Issue 2979 -\n Fixed an issue that could cause the derived invokable declaration index to fail indexing, resulting in\n constant \"Analyzing\" behavior.\n
\n - Added support for aer-based integration test execution with aer\n 1.2.0+.\n
\n - Added support for Agent Script's
subagent directive type including code completion,\n reference navigation, syntax highlighting, etc.\n \n - Fixed an issue where class methods weren't being included in
System.Label variant\n completions.\n \n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":32616303,"downloads":2274,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.1.5","RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]},{"id":1078632,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1078632","version":"2.4.0.8","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1781553756000","file":"10253/1078632/IlluminatedCloud2.zip","notes":"\n 2.4.0.8
\n \n - Issue 2974 -\n Summer '26 / API v67.0 update\n
\n - Updated the SOAP client for API v67.0.
\n - Updated the API version used for primary communication with Salesforce APIs to 67.0.
\n - Added 67.0 as an available API version number for configured connections.
\n - Updated
metadata.xsd based on the API v67.0 Metadata API SOAP WSDL. \n - Updated the OST version number to prompt regeneration for system API changes in Summer '26.
\n - Updated the bundled
completions?type=apex Tooling REST API response to be based on\n the API v67.0 REST endpoint.\n \n - Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '26 changes.\n
\n - Updated the bundled SLDS CSS and SVG icons to 2.30.4.
\n - Updated for new org features, standard value set names, metadata XML file type extensions, etc.
\n - Updated all integrated API documentation.
\n - Usages of SOQL
WITH SECURITY_ENFORCED in Apex source files with API version 67.0+\n are now flagged as errors with a quick-fix to use WITH USER_MODE instead.\n \n - Apex classes with API version 66.0+,\n
@InvocableMethod-/@InvocableVariable-annotated members, and\n parameterized constructors but no no-arg constructor are now flagged as errors with a quick-fix\n to add a no-arg constructor. Note that these classes are deployed/compiled without errors but\n yield errors at runtime when used in an invocable context.\n \n - Added full support for\n Apex integration tests\n (developer preview). Apex unit tests and integration tests have been rationalized into a single\n run configuration type with the same general features as traditionally present for Apex unit\n tests. There is now a test type discriminator on each run config that acts as an\n effective filter for the types of tests associated with that run config as one of:\n
\n - Unit - The run config only executes Apex unit tests.
\n - Integration - The run config only executes Apex integration tests.
\n - Unspecified - Either Apex unit tests or integration tests can be executed by the\n run config, but due to current API restrictions, only one type of test can be included\n in a specific execution. If only unit tests or only integration tests are found for the\n run config when requested for execution, those tests are executed automatically. If\n both types of tests are found, the user is prompted which to execute with an option to\n set that as the run config test type going forward.\n
\n
\n Existing Apex unit test run configs are automatically grandfathered as being for unit tests.\n Context configurations that are based on one type of test, e.g., those for a specific test\n class or method, are automatically configured for that type. It's possible to change the test\n type for a run config in the run config editor as long as it's not inherently inferred from the\n scope of that run config. Note that run configurations for both unit tests and integration tests\n are called Apex Unit Tests in the IDE's run configuration editor because changing\n the run config type name to be more general caused issues with existing Apex unit test run\n configs.\n
\n
\n Note that integration tests do not generate code coverage, so Run with Coverage\n executors are not available for integration test-specific run configs. If an unspecified-type\n run config is executed for coverage for integration tests, the user is notified that coverage\n was not collected and will not be displayed.
\n
\n It is also not yet possible to execute integration tests with Apex Execution Runtime / aer via\n its command-line interface. I've spoken with October Swimmer about this and, once it is possible\n to execute integration tests via the command-line, I will enable that feature in IC.
\n
\n \n - Added full support for\n Apex multiline strings:\n
\n - Updated the Apex parser for multiline strings.
\n - Added multiline string-specific syntax highlighting that clearly shows the boundaries of\n multiline string contents even when indented.\n
\n - Added support for formatting of multiline strings. By default, multiline strings are\n indented at one more than the current statement's indentation level, but they can be\n aligned with the first column if desired. The Apex formatter option that controls this\n behavior is\n Settings | Editor | Code Style | Apex | Tab and indents | Allow multiline strings in first column\n and is enabled by default.\n
\n - Added support for template-driven multiline strings using the new\n
String.template(Map<String, Object>) method:\n \n - Template variable references of the form
${name} are highlighted\n distinctly in multiline strings.\n \n - Template variable references that resolve to a key in the template map can be\n navigated. Unfortunately this navigation is currently one-way and doesn't result\n in selection highlighting or the ability to find usages of template keys. I hope\n to resolve those limitations shortly.\n
\n - Code completions are offered in template variable references for template map\n keys.\n
\n - IC includes two new live templates for generation of template-driven multiline\n strings:\n
\n mlst - Generates a string variable declaration\n initialized with a template-driven multiline string, e.g.:\n String str = '''\n <caret>'''\n .template(new Map<String, Object> {\n\n });mlsti - Same as above but with a\n language injection comment above the declaration so that the IDE\n treats the multiline string's contents as being a document in that\n language, e.g.:\n // language=<languageId>\nString str = '''\n <caret>'''\n .template(new Map<String, Object> {\n\n });
\n \n - I'm also likely going to add a code intention / quick-fix to convert\n concatenated Apex strings into multiline strings with a template if necessary\n for non-string literal expression components of the concatenation. That didn't\n quite fit into this build, but it's on my TODO list.\n
\n
\n \n - The latter live template demonstrates an incredibly powerful JetBrains IDE\n feature that's particularly useful with multiline strings (though it also works well\n with concatenated single-line strings),\n language injections.\n Given that one of the primary use cases for multiline strings is to host content in\n other languages such as SOQL, SOSL, JSON, and XML, it's exceptionally useful to be able\n to leverage the IDE's first-class support for the associated language when working with\n that content. The easiest way to do this in a durable manner is by adding a line comment\n of the form:\n
// language=<languageId>
apex.\n \n
\n \n
\n
\n \n - Issue 2973 -\n Fixed an issue that could prevent the new metadata format project wizard from displaying properly.\n
\n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":32617630,"downloads":3148,"pluginId":10253,"compatibleVersions":{"PHPSTORM":"2025.2.6.1 — 2026.1.5","RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5"},"author":{"id":"d3a57bf0-3424-4759-a4c6-ef1911026813","name":"Scott Wells","link":"/author/d3a57bf0-3424-4759-a4c6-ef1911026813","hubLogin":"illuminatedcloud","icon":"https://hub.jetbrains.com/api/rest/avatar/d3a57bf0-3424-4759-a4c6-ef1911026813","showMarketoCheckbox":true},"modules":[]}]