2.3.7.5 release notes
2.3.7.5
- Issue 2847 - Prospective fix for an issue observed in user-provided log extracts where IC is attempting to cache a namespace for an invalid, non-null element. This could well be a downstream side-effect of an another issue. If so, I'll continue to work with the reporting users to find and fix the ultimate root cause.
- Issue 2848 - Added a new tab-level option to the SOQL Query tool window to disable query validation specifically for that tab. This is useful when a query would be flagged by certain validations, e.g., as having unconstrained sub-queries, but the user knows that the query will execute without issue. It allows validation to be disabled for exactly those queries while remaining enabled in general. Validation can be enabled/disabled via a toolbar toggle button and via a checkbox in all of the actual validation dialogs.
- Issue 2849 - Added aggressive caching of node IDs in the build options dialog as a prospective fix for yet another "Illuminated Cloud might be slowing things down" report.
- Issue 2850 - Added full support for Apex methods annotated as
@AuraEnabled(Continuation=true)
, particularly in LWC where those methods should be imported as@salesforce/apexContinuation
instead of@salesforce/apex
. References are added to@AuraEnabled
methods assigned toSystem.Continuation.continuationMethod
to ensure relational integrity, and method name completions are offered for assigned string literals. This change also includes a new LWC import live template,importapexcont
, that generates an appropriate ES6/TypeScriptimport
statement for such a method. - Added a quick fix to the Apex Unresolvable reference code inspection when the reference appears to be specifically to a custom SObject type, field, or reference to regenerate the SObjects portion of the offline symbol table instead of creating a new local declaration with that name.
- The Salesforce Code Analyzer external annotator's Show progress indicator option is now disabled by default. You can always re-enable it explicitly if you'd like, but based on my own personal preference and that of several users who have inquired about how to disable it, I've decided that it's probably better to default to a less "noisy" setting.
Dev Agent Integration
I've been spending considerable time investigating how best to integrate the new Dev Agent features into IC. Progress for that effort is being tracked in issue 2843. I've also been speaking directly to Salesforce about whether/how other capabilities might be more directly integrated, though I don't have anything concrete to share at present. I'll provide additional details via the issue linked above as they become available. For now, though, it's primarily about how to extend existing agentic/generative AI tools for JetBrains' IDEs to use Salesforce's MCP server.