[{"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":2964,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.2.2","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.2.2","WEBSTORM":"2025.2.6.1 — 2026.2.2","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.2","PYCHARM":"2025.2.6.1 — 2026.2.2"},"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":2493,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.2.2","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.2.2","WEBSTORM":"2025.2.6.1 — 2026.2.2","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.2","PYCHARM":"2025.2.6.1 — 2026.2.2"},"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":2211,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.2.2","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.2.2","WEBSTORM":"2025.2.6.1 — 2026.2.2","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.2","PYCHARM":"2025.2.6.1 — 2026.2.2"},"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":1139,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.2.2","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.2.2","WEBSTORM":"2025.2.6.1 — 2026.2.2","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.2","PYCHARM":"2025.2.6.1 — 2026.2.2"},"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":2607,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.2.2","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.2.2","WEBSTORM":"2025.2.6.1 — 2026.2.2","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.2","PYCHARM":"2025.2.6.1 — 2026.2.2"},"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":2386,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.2.2","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.2.2","WEBSTORM":"2025.2.6.1 — 2026.2.2","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.2","PYCHARM":"2025.2.6.1 — 2026.2.2"},"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":1995,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.2.2","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.2.2","WEBSTORM":"2025.2.6.1 — 2026.2.2","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.2","PYCHARM":"2025.2.6.1 — 2026.2.2"},"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":1447,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.2.2","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.2.2","WEBSTORM":"2025.2.6.1 — 2026.2.2","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.2.2","PYCHARM":"2025.2.6.1 — 2026.2.2"},"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":2087,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":2272,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":3147,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":1070218,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1070218","version":"2.4.0.7","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1780942123000","file":"10253/1070218/IlluminatedCloud2.zip","notes":"\n 2.4.0.7
\n Minor bug fix release before next week's Summer '26 updates:\n \n - Issue 2968 (redux) -\n Improved fix for an NPE when copy/pasting files to the IDE project.\n
\n - Issue 2972 -\n Addressed an potentially significant IDE memory growth issue introduced accidentally in the last few\n builds where IC's server metadata index could be included once per-file in what should otherwise be a\n very slim file-to-metadata cache.\n
\n - Several other minor fixes.
\n
\n Also, if you are having issues with validation and code completion in Salesforce metadata XML files in 2026.1,\n it appears to be a regression in the base JetBrains IDE, and I've logged a\n bug in their public issue\n tracker that clearly shows the correct behavior in 2025.3 and earlier and incorrect behavior in 2026.1.\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":32731669,"downloads":2243,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":1067149,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1067149","version":"2.4.0.6","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1780592139000","file":"10253/1067149/IlluminatedCloud2.zip","notes":"\n 2.4.0.6
\n \n - Issue 2964 -\n Fixed an issue where
AbstractFileType files were being processed incorrectly during\n indexing.\n \n - Issue 2965 -\n Fixed an issue where compiled LWC TypeScript
*.js files weren't being properly added to\n deployment payloads.\n \n - Issue 2966 -\n Increased the LWC TypeScript compilation timeout from 30 seconds to 5 minutes. If you still see\n TypeScript compilation timeouts, please let me know so that I can either raise it further or make it\n configurable.\n
\n - Issue 2968 -\n Prospective fix for an NPE when copy/pasting files to the IDE project. I say \"prospective\" because I've\n not been able to reproduce it, but the nature of the NPE is clear from the stack trace, and I've updated\n that logic to be defensive and use the original, non-null parameter value when necessary.\n
\n - Implemented a number of quality-of-life fixes and improvements:\n
\n - With the changes to IC in\n 2.4.0.5\n to accommodate for how CLI-based connection access tokens are made available to clients, it was\n necessary for IC to query the access token for a project from the CLI the first time it was\n needed after opening the project. While not a huge issue, this could result in a bit of a\n general workflow slow-down when, for example restarting the IDE. IC now includes an\n opt-in feature to store access tokens securely in the host JetBrains IDE's\n Password Safe.\n When enabled, the access token behavior is effectively the same as before 2.4.0.5, but now\n stored securely in either the OS' native keychain or KeePass. This option is\n disabled by default but can be enabled via\n Illuminated Cloud | Configure Application | Salesforce DX | Store access tokens in Password Safe.\n Note that the IDE's Settings | Appearance & Behavior | System Settings | Passwords\n option must be set to save passwords in a persistent location, either\n In native Keychain (Mac and Linux only) or In KeePass (all OSes). If the\n Do not save, forget passwords after restart option is selected, IC will only save access\n tokens in its own in-memory cache for the lifetime of the running IDE process.\n
\n - In IDEs with first-class support for JavaScript — basically any commercial IDE or any\n free 2026.1+ IDE — IC now uses the IDE's native npm dependency versioning features to\n determine whether or not dependencies are up-to-date. In IDEs without first-class support for\n JavaScript, IC now compares
package.json to the contents of\n node_modules to determine dependencies status, though again, I recommend all users\n pairing IC with a free JetBrains IDE update to 2026.1+.\n \n - Improved console view message formatting in the Anonymous Apex, SOQL Query, and SOSL Query tool\n windows.\n
\n - Improved fenced code block formatting in ApexDoc comments.
\n - Implemented what I hope to be a pretty significant performance optimization around one of IC's\n main reference contributors. In addition to helping with bulk operations like project-wide\n inspection runs, it should also help noticeably with editor symbol highlighting responsiveness\n and similar.\n
\n - The contents of
.illuminatedCloud/lwc/types are no longer generated unconditionally\n when a project is opened. Instead IC checks whether or not those contents are out-of-date\n relative to the associated source files and only generates what's necessary to bring them\n up-to-date. This should generally eliminate the need for an additional indexing pass shortly\n after opening a project.\n \n - Implemented several behavioral improvements for modal progress indicators executed in the\n context of modal dialogs.\n
\n - Fixed an issue with several combo-boxes where selection change events would be fired while using\n the keyboard to move through options before committing a new selection.\n
\n - Fixed an issue with finding the correct editor when the tabbed editor UI is enabled and the\n selected editor tab is not the primary file for that tabbed editor.\n
\n
\n \n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":32730909,"downloads":2046,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":1057773,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1057773","version":"2.4.0.5","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1779830153000","file":"10253/1057773/IlluminatedCloud2.zip","notes":"\n 2.4.0.5
\n \n - Salesforce CLI issue 3560 -\n IMPORTANT: The Salesforce CLI is in the process of implementing a set of security mitigation\n changes, some of them with breaking behavior. Starting with this build, IC accommodates for the\n changes around how connection access tokens are made available via CLI commands. For pre-2.136.8\n CLI versions, IC will use continue to the
org list and org display commands to\n get CLI-based connection access tokens; for 2.136.8+ CLI versions, IC will use the\n org auth show-access-token command. IC automatically determines the installed CLI version\n and, for efficiency, caches that value aggressively, though it should be resilient to CLI\n upgrades/downgrades while running.
\n
\n In support of Salesforce's goal of not having access tokens stored in-the-clear in the file system,\n IC no longer caches them persistently across IDE sessions. They are still cached aggressively in-memory,\n but if/when the IDE is restarted, IC will need to fetch access tokens for CLI-based connections using\n the respective CLI command(s) when first needed and again, of course, when they become stale.
\n
\n Additionally the option\n Illuminated Cloud | Configure Application | GraphQL | Include connection information now defaults\n to disabled, though you can always enable that option if you'd like, understanding that it will\n result in the current CLI connection's access token being written to the project's\n graphql.config.yml file.
\n
\n IC should not be including CLI access tokens in idea.log unless debug logging is explicitly\n enabled by the user for the respective logging channels. It is, of course, recommended that such debug\n logging only be enabled as required for diagnostic purposes and disabled again when no longer needed.
\n
\n \n - Issue 2959 -\n Fixed an issue where Apex test failures that weren't directly attributable to an executed test class\n and/or method weren't being included in the test results when executed synchronously.
\n
\n While working on this, I fixed a number of other issues with failed test status attribution when the\n API's test results failed to include complete attribution information. This should result in much better\n diagnostics for Apex tests which fail due to transitive issues such as inconsistent server-side Apex\n compilation state, particularly with asynchronous test execution.
\n
\n \n - Issue 2960 -\n Improved error handling when an MCP servers JSON file fails to load/parse.\n
\n - Issue 2962 -\n Implemented a set of prospective fixes/improvements for some freezes/slow-downs that users have\n reported. If you continue to see such problems, please let me know so that I can gather diagnostic\n information and address them.\n
\n - Fixed an issue with a breaking API change in LSP4IJ. If you see issues with LSP4IJ, please make sure\n that you have the latest plugin version installed.\n
\n - Fixed a potential
IndexNotReadyException during deployment. \n - Fixed an issue with Agentforce for Developers inline completions due to a breaking API change.
\n - Fixed a \"Reentrant indexing\" issue that could occur when building the Apex derived declarations indexes.\n Note that in the process of verifying these changes, I noticed that the IDE is sometimes showing\n duplicate line markers for inheritance relationships. I've logged a corresponding\n bug with JetBrains.\n
\n - Added a few metadata types to
metadata.xsd observed as missing/undefined in open source\n reference/test projects.\n \n - Added reference support for invocable variable targets in\n
*.invocableactionextension-meta.xml files.\n \n - Implemented numerous new project wizard UX improvements and refinements.
\n - Improved performance of Apex test/tested related class navigation.
\n - Improved IC intention categorization in Settings | Editor | Intentions.
\n - Another set of under-the-hood improvements and optimizations.
\n
\n Other news
\n \n - The next two major items on my plate are (still):\n
\n - Salesforce Summer '26 updates to ensure they're ready for the final platform release in a bit\n under a month.\n
\n - Moving the public issue tracker and IC user guide from Bitbucket to GitHub well before the\n August 20, 2026 deadline.\n
\n
\n \n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":32722381,"downloads":3082,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":1051016,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1051016","version":"2.4.0.4","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1779121940000","file":"10253/1051016/IlluminatedCloud2.zip","notes":"\n 2.4.0.4
\n \n - Issue 2951 -\n Added first-class support for\n UI Bundles and Salesforce Multi-Framework.\n Note that this feature requires native IDE JavaScript/TypeScript/CSS/React support, so you'll need to\n pair Illuminated Cloud with either a commercial JetBrains IDE or a free 2026.1+ JetBrains IDE. A\n demonstration video is available here.
\n
\n As part of this work, the Illuminated Cloud application-level settings tab LWC has been renamed\n UI Frameworks and now includes options for configuration of both Lightning Web Components and UI\n Bundles behavior. The new/changed options are:\n \n - LWC\n
\n - Enable LWC local development - LWC local development support has existed for some\n time, but it wasn't possible to disable it. Now it can be disabled if desired, but it is\n enabled by default.\n
\n - Disable deploy-on-save of LWC source files when the local development server is running -\n This option was moved from the Deployment tab (previously called\n Validation and Deployment) to be closer to its related settings. The behavior is\n unchanged.\n
\n
\n \n - UI Bundles\n
\n - Build UI bundles on deployment - When enabled, automatically runs\n
npm run build for UI bundles included in a deployment request to bring them\n up-to-date before deploying them. If that build fails, the deployment request fails fast\n and the errors are reported. Enabled by default.\n \n - Only build out-of-date bundles - When enabled, UI bundles are only built on\n deployment if they appear to be out-of-date based on a comparison of UI bundle's main\n files' last modified timestamps against those in the UI bundle's
build and\n dist sub-directories. Enabled by default, but if you use tools that\n change files' last modified dates explicitly, e.g., when they are reverted in version\n control, you may need to disable it.\n \n - Enable UI bundle local development - Analogous to the same feature for LWC above.\n When enabled, context actions are added to help start, restart, and stop a local\n development server for each UI bundle. Enabled by default.\n
\n - Disable deploy-on-save of UI bundle files when the local development server is running -\n Again, this is analogous to the same feature for LWC above. When enabled and a UI bundle\n local development server is running, deploy-on-save is automatically disabled for that\n UI bundle's files. Enabled by default.\n
\n - Open the local development server as: [External | Internal | Internal split] -\n Determines where/how the browser is opened when a local development server is started\n for a UI bundle as one of:\n
\n - External - The IDE's configured default browser is used.
\n - Internal - An IDE editor tab is used or reused if it already exists.
\n - Internal split - An IDE editor tab is used or reused if it already exists\n as a right-side split.\n
\n
\n The default is Internal split as that works very nicely for a real-time preview.\n \n
\n \n - Unit Tests - These are effectively the same configuration options added recently for\n LWC Jest test execution in free 2026.1+ JetBrains IDEs, but extended to support both LWC Jest\n tests and UI Bundle Vitest tests.
\n
\n Note that I've found that, at least on Windows, DAP-based debugging of Vitest tests works with\n vite 5.x, 6.x, and 8.x, but for some reason it doesn't seem to work properly with\n 7.x. If you find that the DAP-based debugger is never stopping at your test code breakpoints,\n try changing the vite version in the UI bundle's package.json file\n and running npm install.
\n
\n I've also found a\n few other issues\n with UI bundles specific to Windows/ARM64. The workarounds are described in the logged issue.\n \n
\n
\n As stated above, it's now possible to start, restart, and stop local development servers for UI bundles\n from any source file in those bundles using Alt/Opt+Enter context actions or right-click context\n menu actions. Changes made locally should be reflected in the local development preview nearly\n instantaneously.
\n
\n IC now includes a File | New | UI Bundle action that prompts for:\n \n - Name - The UI bundle's symbolic name.
\n - Template - The template upon which the resulting bundle is based, currently either\n Default which is basically empty and React basic which is a boilerplate stub\n for a Salesforce platform-aware React application. React basic by default.\n
\n - Run 'npm install' - Whether or not to run
npm install from the UI bundle\n directory immediately after creating the new bundle. Enabled by default.\n \n
\n
\n UI Bundles support should be considered beta-level given that the underlying UI Bundles feature\n itself is also beta.
\n
\n \n - Added structure view and Next/Previous Method navigation in Jest and Vitest test files.
\n - Added browser type selection support to the Generate ApexDoc and Save Flow Diagram\n actions. In both cases, the last selected browser type for a given action is retained across\n invocations.
\n
\n Note that I'm currently unable to add support to the LWC local development server Start action\n because it insists on opening the browser itself. I've reported that to Salesforce, asking if an option\n can be added to the associated command to have it output the URL to be opened just as with the\n sf org open command.
\n
\n \n - IC now properly processes nested
.forceignore files. \n - Message view tabs created by Illuminated Cloud for executed sub-processes now retain ANSI formatting\n from those processes, and also use ANSI formatting for section headers.\n
\n - Implemented a number of fixes, refinements, and optimizations around new project creation and initial\n project configuration.\n
\n - Fixed a few issues with how IC determines whether or not the host JetBrains IDE provides first-class\n support for JavaScript, TypeScript, and CSS.\n
\n - I know I say this frequently, but this build includes a significant set of other under-the-hood\n fixes and improvements. If you find any issues or regressions, please let me know and I'll address them\n ASAP.\n
\n
\n Other news
\n \n - The next two major items on my plate are:\n
\n - Salesforce Summer '26 updates to ensure they're ready for the final platform release in about\n a month.\n
\n - Moving the public issue tracker and IC user guide from Bitbucket to GitHub well before the\n August 20, 2026 deadline.\n
\n
\n \n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":32690674,"downloads":2788,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":1036326,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1036326","version":"2.4.0.3","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1777569233000","file":"10253/1036326/IlluminatedCloud2.zip","notes":"\n 2.4.0.3
\n \n - Issue 2919 (redux) and\n Issue 2955 -\n Improved handling of references to
*-meta.xml files when those files are renamed,\n particularly in other XML files such as package.xml and permission sets/profiles.\n \n - Issue 2949 -\n Prospective fix for an issue where loaded scratch org definition files in the create scratch org dialog\n could be based on stale cached information.\n
\n - Issue 2952 -\n Improved Apex offline debugger source position determination when stub/synthetic declarations are\n involved, e.g., default no-arg constructors.\n
\n - Issue 2956 -\n Fixed an issue where Apex coverage would not be displayed properly after unit test execution.\n
\n - Extended IC's assisted installation/configuration support for agentic AI tools to include more agentic\n AI JetBrains plugins and more/more recent Salesforce-specific support components. A demonstration video\n is available here.
\n
\n In Illuminated Cloud | Configure Application | Agentforce, the Agentforce Vibes section\n has been renamed Vibe Coding to reflect this more general support for agentic AI tools, and it\n now includes a tabbed interface with support for:\n \n IC assists with installation and configuration of each of these agentic AI tools including:\n \n - Plugin installation/enablement
\n - Salesforce DX MCP server\n configuration\n
\n - Salesforce hosted MCP servers\n configuration - See below for additional details.\n
\n - Salesforce-specific rules - Note that the bundled rules have been updated significantly vs.\n earlier versions of this integration to include those that guide the tools toward proper and\n consistent usage of the Salesforce MCP servers and bundled skills.\n
\n - Salesforce-specific\n skills\n
\n
\n In general IC tries to add project-independent configuration at the user-level (i.e., under the user\n home directory) and project-specific configuration at the project-level (i.e., under the project root\n directory). However, based on each tool's own preferences and limitations, there are some tool-specific\n variances. IC shows the configuration scope of each tool/configuration combination, and once installed,\n the scope acts as a link to the actual configuration file(s).\n
\n
\n Salesforce hosted MCP servers considerations
\n The Salesforce hosted MCP servers generally require\n configuration of an External Client App (ECA)\n for MCP client authentication and authorization. In order to simplify these turnkey tool integrations,\n IC provides an option to Authorize Salesforce hosted MCP server requests automatically using its\n configured Salesforce org connections. This option is disabled by default, but when enabled, IC\n automatically queries the active MCP servers from the connected organization — and provides a\n convenient link to configure the org's active MCP servers if necessary — and configures the\n agentic AI tools to proxy all Salesforce hosted MCP server requests through IC so that those requests\n can be automatically decorated with IC's authorization header. Note that this proxy behavior\n does not inspect, capture, or otherwise compromise the contents of the proxied requests and\n responses, and all communications with the Salesforce hosted MCP servers are, of course, performed over\n HTTPS/SSL.\n \n - Many other fixes and improvements.
\n
\n Other news
\n \n - The next major task will be adding full, first-class support for the new
UIBundle metadata\n type and the associated on-platform support for React. Again, React is also now supported by the free\n JetBrains 2026.1 IDEs, so once this feature has been delivered, all IC users should have access to a\n quite complete set of React/Salesforce development tools.\n \n - I realize this is a repeat, but in the spirit of overcommunicating important things, after that I'm\n planning to begin moving the public issue tracker and IC user guide from Bitbucket to GitHub in earnest.\n If you've visited either of those recently, you've no doubt seen the header banner about those being\n shut down on August 20, 2026, but I plan to have things migrated well in advance of that date. Feel free\n to continue using them in their current locations between now and the move, though, as they continue to\n be fully operational in the interim. As before, if you'd like your issue tracker activity reflected in\n the new issue tracker, please provide your Bitbucket and GitHub user IDs so that I can include them in\n the user mapping.\n
\n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":32496479,"downloads":3001,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":1031026,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1031026","version":"2.4.0.2","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1776961445000","file":"10253/1031026/IlluminatedCloud2.zip","notes":"\n 2.4.0.2
\n \n - Issue 2950 -\n Updated the
*scratch-org-def.json JSON schema for the latest-and-greatest settings types.\n \n - Added support for aer-based profiling of executed unit tests via the\n Profile \"Run Configuration Name\" with aer Apex unit test executor. After aer test\n execution, the resulting profiling snapshot is automatically opened in the\n Perfetto trace viewer for review. Note that\n aer is a different Apex runtime than the Salesforce server and will have different performance\n characteristics, though the resulting profiling data should hopefully be directionally useful. It can,\n of course, also be used to understand aer-based test execution hotspots and bottlenecks. To profile\n org-based execution, use the Salesforce server Apex unit test profiling executor and IC's Log Analyzer.\n
\n - Added another aer unit test execution configuration option to add the
--skip-errors option\n always when aer is executed. This option is enabled by default to help ensure more reliable aer\n unit test execution even when the project metadata may not be in a 100% consistent state, or when the\n project contains references that are not yet fully supported by aer.\n \n - Added support for Select In | Coverage from an Apex production source file when the coverage view\n is active.\n
\n - Fixed an issue with Agentforce for Developers where the Salesforce API was requiring a new header for\n requests resulting in the error\n
REQUIRED_FIELD_MISSING (E20008) - The x-client-feature-id header doesn't contain a valid feature identifier.\n \n - Numerous other fixes and improvements.
\n
\n Other news
\n \n - Last week I attended TDX 2026 and soaked in the new features, enhancements, etc., coming to the\n Salesforce platform, both immediately and over the next several releases. I'm already well into\n the implementation of two signigicant near-term enhancements from TDX:\n
\n - I'm updating IC's assisted Cline and Kilo Code integration for Salesforce skills, hosted MCP\n servers now that they're GA, and updated rules to make all of that work together nicely. I'll\n also be updating the documentation for how to use all of those in other JetBrains agentic AI\n plugins such as JetBrains Junie, GitHub Copilot, Claude Code, Windsurf, and Zencoder.\n
\n - I'm adding full, first-class support for the new
UIBundle metadata type and the\n associated on-platform support for React. Note that React is also now supported by the free\n JetBrains 2026.1 IDEs.\n \n
\n \n - Over the next few weeks, I'll also begin moving the public issue tracker and IC user guide from\n Bitbucket to GitHub in earnest. If you've visited either of those recently, you've no doubt seen the\n header banner about those being shut down on August 20, 2026, but I plan to have things migrated well\n in advance of that date. Feel free to continue using them in their current locations between now and\n the move, though, as they continue to be fully operational in the interim. As before, if you'd like\n your issue tracker activity reflected in the new issue tracker, please provide your Bitbucket and\n GitHub user IDs so that I can include them in the user mapping.\n
\n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":31943923,"downloads":2775,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":1014712,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/1014712","version":"2.4.0.1","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1775751373000","file":"10253/1014712/IlluminatedCloud2.zip","notes":"\n 2.4.0.1
\n \n - As noted in the previous release notes, starting with 2026.1, free JetBrains IDEs now include\n first-class language support for\n JavaScript, TypeScript, and CSS\n (i.e., without an active JetBrains subscription). Also as stated previously, the main things that are\n notably missing are the JavaScript debugger and Jest support, but I've addressed those omissions in IC.\n A demonstration of these features is available\n here.
\n
\n Note that the items described below are only available in free JetBrains 2026.1+ IDEs. All\n commercial JetBrains IDEs already have their own versions of the same features, and they will not\n work with earlier free JetBrains IDEs because they build on the 2026.1+ IDEs' free JavaScript and\n TypeScript support. Users pairing IC with a free JetBrains IDE are strongly encouraged to use\n 2026.1+ going forward.
\n
\n With that preface out of the way, IC now includes first-class support for execution\n (including continuous feedback via a watch runner), interactive debugging, and\n coverage analysis of LWC Jest tests. There are several pre-reqs including Node, Jest, and\n LSP4IJ (for DAP-based interactive debugging), but as usual, IC will help install and configure them as\n needed. Once installed, these features work pretty much exactly like they would for any other\n language/framework, with full integration into the IDE's project and editor views.
\n
\n There are several new application-level configuration options under\n Illuminated Cloud | Configure Application | LWC | Unit Tests (again, free JetBrains 2026.1 IDEs\n only):\n \n - Integrate Jest (free IDEs 2026.1+) - Allows the entire feature to be enabled or disabled\n if desired. Defaults to enabled.\n
\n - Enable Jest 'Run' executor - Adds the ability to run Jest tests. Defaults to\n enabled.\n
\n - Enable Jest 'Watch' executor - Adds the ability to run Jest tests continuously. Defaults\n to enabled.\n
\n - Watch type - Sets the watch type to be used by the Watch executor as\n either\n
--watch\n or\n --watchAll.\n Defaults to --watch.\n \n - Disable deploy-on-save when Jest 'Watch' is running - Automatically disables IC's\n deploy-on-save feature when a Watch executor is actively running. Defaults to\n enabled.\n
\n
\n \n - Enable Jest 'Run with Coverage' executor - Adds the ability to run Jest tests and\n gather/analyze the associated coverage metrics. Defaults to enabled.\n
\n - Enable Jest 'Debug' executor - Adds the ability to debug individual Jest tests. Defaults\n to enabled.\n
\n - JavaScript DAP debugger - The path to the\n JavaScript/TypeScript\n DAP debugger distribution. The field label is a link to the latest release.\n
\n
\n \n
\n
\n The new Jest run configuration type includes the following options:\n \n - Jest config file (optional) - The path to the Jest config file, typically\n
jest.config.js immediately under the project root. If found there, IC will\n automatically use that as the default.\n \n - Jest options (optional) - Additional Jest command-line options if desired. Of course,\n be careful not to create an invalid command-line, either by using incorrect options or by\n trying to override the options supplied by IC itself.\n
\n - Scope - The scope of Jest tests to be executed for the run configuration as one of:\n
\n - All tests - Executes all LWC Jest tests in the project.
\n - Directory - Executes all LWC Jest tests under a specific directory.
\n - File - Executes all tests in a specific LWC Jest test file.
\n - Suite - Executes all tests in a specific LWC Jest test file/suite.
\n - Test - Executes a specific LWC Jest file/test.
\n
\n \n
\n Jest run configurations can be created explicitly or contextually using gutter or context actions on\n the respective directories, files, test suites, or tests. As with Apex unit test run configurations,\n Jest context configurations are read-only but can be duplicated as writable run configurations if\n desired.
\n
\n The following executors are available for Jest run configurations:\n \n - Run - Executes all tests for the run configuration and displays results in the IDE's\n standard tool window.\n
\n - Watch - Executes tests for the run configuration using Jest's watch feature based on the\n aforementioned application-level configuration. The respective tests are automically re-run and\n test results displayed based on local source files changes. Also as described above, you can\n disable deploy-on-save when a Watch run configuration is active to streamline the local\n continuous feedback loop.\n
\n - Run with Coverage - Executes all tests for the run configuration, displays results in the\n IDE's standard tool window, and displays coverage information for the respective JavaScript and\n TypeScript source files in the IDE's standard coverage view, project view, and editor. Coverage\n is reported and integrated at the line-, statement-, function-, and logical branch-levels.\n Partially-covered branching logic is displayed in the editor in yellow (as opposed to green and\n red), and by clicking on the yellow gutter annotation, you can see the number of hits for each\n branch.\n
\n - Debug - Executes a single Jest test in the IDE's interactive debugger. This requires\n LSP4IJ's DAP support and the JavaScript DAP debugger. IC will help install both of these\n components if not detected.\n
\n
\n
\n With these gaps filled, the combination of IC and a free JetBrains 2026.1+ IDE should provide a\n very complete Salesforce development feature set. I'd be very interested to know if you find any\n other missing features given this specific combination.
\n
\n \n - Issue 2944 -\n Added scheduled paths to Mermaid flow diagrams.\n
\n - Issue 2947 -\n Fixed a class of errors that could potentially occur with stub virtual files.\n
\n - Issue 2948 -\n Properly denoted
Auth.OauthToken.revokeToken() as static. The OST must be\n regenerated to see the effect of this change.\n \n - In the process of implementing Jest support, I also implemented a number of improvements for Apex unit\n test execution including a test-specific index that should remove the need to enumerate Apex test files\n exhaustively in the Apex unit test run configuration editor and elsewhere.\n
\n - When bundled docs are shown for an overloaded standard Apex method, all signatures are displayed due to\n a lack of signature-specific anchors in the source material. To help minimize signature confusion, IC\n now clearly states this to be the case and cautions the user to consult the appropriate section for the\n desired signature.\n
\n - Quite a few other fixes and improvements.
\n
\n ","since":"252.28539.33","until":"261.*","sinceUntil":"252.28539.33 — 261.*","channel":"","size":31855608,"downloads":2805,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.2.6.1 — 2026.1.5","PYCHARM_COMMUNITY":"2025.2.6.1 — 2025.3","PHPSTORM":"2025.2.6.1 — 2026.1.5","WEBSTORM":"2025.2.6.1 — 2026.1.5","IDEA_COMMUNITY":"2025.2.6.1 — 2025.3","IDEA":"2025.2.6.1 — 2026.1.5","PYCHARM":"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":997589,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/997589","version":"2.4.0.0","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1774540937000","file":"10253/997589/IlluminatedCloud2.zip","notes":"\n 2.4.0.0
\n \n - Issue 2939 -\n Fixed an issue that could occur when an error is reported for a source file by the API or CLI with a\n simplified path, e.g.,
classes/Foo.cls, where the local path is more complex, e.g.,\n classes/subfolder/Foo.cls. Now if no matches are found using the reported path, IC looks\n for a unique source file with the same name and, if found, reports against it.\n \n - Issue 2941 -\n As of 2026.1,\n IntelliJ IDEA includes first-class language support for JavaScript, TypeScript, and CSS\n for free\n (i.e., without an Ultimate subscription). This includes not just basic language support features like\n intelligent code completion, reference navigation, source code formatting, etc., but also extensive\n refactorings, static code analysis including integration of ESLint and Stylelint, tight npm integration,\n and much more.
\n
\n The main things that are notably missing are the JavaScript debugger and Jest support, but I'm working\n on a very tight integration of those now using LSP4IJ's DAP support and the DAP JavaScript debugger,\n specifically in support of Jest unit test execution, interactive debugging, and (hopefully) code\n coverage.
\n
\n IC now automatically detects this specific IDE state (unlicensed 2026.1+ IntelliJ IDEA) and enables all\n of the JS/TS/CSS-specific plugin extension points that would have previously only been enabled in\n licensed IDEs. IC also helps associate JS and CSS files with their native file types and disable any\n configured LSP4IJ language servers that were providing support for those languages in earlier free IDEs.\n \n - Issue 2943 -\n Fixed a \"Comparison method violates its general contract\" error that could occur in (large?) metadata\n retrievals in source format projects while sorting the retrieve results.\n
\n - Added support for an Apex unit test execution continuous feedback loop via Apex Execution Runtime\n (aer)'s support for\n test-driven development.\n When aer is integrated, IC now includes a Watch with aer Apex unit test executor that runs all\n tests in the specified run configuration, then automatically re-runs them when project source files are\n modified, displaying new test results (typically) in near-real-time thanks to aer's incremental\n compiler. This cycle continues until/unless explicitly stopped by the user. A demonstration video\n is available here.
\n
\n This feature includes two new application-level configuration options in\n Illuminated Cloud | Configure Application | Apex | Apex Execution Runtime (aer):\n \n - Enable 'Watch with aer' - When enabled, the Watch with aer executor is included\n alongside other enabled Apex unit test executors. Enabled by default.\n
\n - Disable deploy-on-save when 'Watch with aer' is running - When enabled alongside\n Enable 'Watch with aer' and a Watch with aer run configuration is actively\n running, deploy-on-save is automatically disabled. It is still possible to deploy metadata\n files using the Force Save and Deploy All/Modified Metadata actions, but simply\n typing Ctrl/Cmd+S will only save files to the local file system — triggering the\n aer watcher — and not the connected Salesforce organization. Enabled by default.\n
\n
\n
\n I have also investigated integrating this with Apex code coverage so that coverage metrics are\n constantly updated, but unfortunately I haven't found a good way to keep the IDE's coverage view open\n across test runs, and the resulting constant opening/closing of the coverage view is quite disruptive.\n I'll keep investigating and will hopefully find a good solution.\n \n
\n ","since":"251.26094.121","until":"261.*","sinceUntil":"251.26094.121 — 261.*","channel":"","size":31692907,"downloads":5318,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.1.2 — 2026.1.5","PYCHARM_COMMUNITY":"2025.1.2 — 2025.3","PHPSTORM":"2025.1.2 — 2026.1.5","WEBSTORM":"2025.1.2 — 2026.1.5","IDEA_COMMUNITY":"2025.1.2 — 2025.3","IDEA":"2025.1.2 — 2026.1.5","PYCHARM":"2025.1.2 — 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":990477,"link":"/plugin/10253-illuminated-cloud-2/versions/stable/990477","version":"2.3.9.9","approve":true,"listed":true,"hidden":false,"recalculateCompatibilityAllowed":true,"cdate":"1773936243000","file":"10253/990477/IlluminatedCloud2.zip","notes":"\n 2.3.9.9
\n \n - Enabled support for the 2026.1 JetBrains IDEs that are now in a\n release candidate state.\n As always, if you see issues with a pre-release IDE build, please revert to the most recent released\n build and let me know about the issues you've seen so that I can address them.\n
\n - Issue 2929 -\n Made sure that the connection icon includes a lock overlay consistently for connections that require\n write confirmation. It was most noticeably missing in the connection status bar widget.\n
\n - Issue 2936 -\n Fixed a
StackOverflowError that could occur when overriding dynamic file types.\n \n - Fixed a few issues with placeholder
*.object-meta.xml files being incorrectly treated as\n full custom object files during metadata deployment and retrieval.\n \n - Improved CLI-based deployment result reporting where some information was being sent to\n
successes and failures instead of files in the JSON result.\n \n - Added support for contextually-correct code completion for aer debugger expressions.
\n - Increased the maximum number of log header rows displayed in the Log Analyzer tool window from\n 100 to 2500. In order to get to >1000 stored logs, I had to lower the logging level to bare minimum and\n execute unit tests repeatedly. At the standard logging level, Salesforce was rolling logs so that only\n about 500 were retained at any given time. Obviously that number will vary widely based on the logs'\n contents, but I feel that 2500 should be a decent limit until/unless I hear otherwise.\n
\n - Fixed an issue where inheritance relationships were incorrectly being applied to
static\n methods.\n \n - Implemented several performance optimizations that are likely most noticeable during batch code\n inspection runs.\n
\n - Quite a few other related fixes and improvements.
\n
\n ","since":"251.26094.121","until":"261.*","sinceUntil":"251.26094.121 — 261.*","channel":"","size":31662299,"downloads":2343,"pluginId":10253,"compatibleVersions":{"RUBYMINE":"2025.1.2 — 2026.1.5","PYCHARM_COMMUNITY":"2025.1.2 — 2025.3","PHPSTORM":"2025.1.2 — 2026.1.5","WEBSTORM":"2025.1.2 — 2026.1.5","IDEA_COMMUNITY":"2025.1.2 — 2025.3","IDEA":"2025.1.2 — 2026.1.5","PYCHARM":"2025.1.2 — 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":[]}]