2.3.5.8 release notes

2.3.5.8

  • Issue 2468 - Implemented a custom diff tool for Salesforce Flow metadata, Flow diagram side-by-side viewer, that displays Mermaid-based diagrams for two Flow revisions or files. This can be accessed in the IDE's internal diff viewer using the diff tool drop-down as an alternative to the standard Side-by-side viewer and Unified viewer options, and are available in any context in which the IDE's internal diff viewer can be used, e.g., VCS version comparison, Local History version comparison, and comparison of two explicit *.flow project files. Please be aware of the following limitations in the current implementation:
    • This diff tool will not be used if the IDE is configured for an external diff tool for the Default file type.
    • Differences between the two Flow revisions/files are not currently annotated explicitly. The diagrams are shown for the respective revisions/files just as they would be in the Flow preview file editor. I am currently considering various ways of annotating differences in this view as a future enhancement.
    • Vertical scroll synchronization is currently percentage-based and does not attempt to correlate nodes between diagrams.
    • If you see the failure message:
      Cannot read field "objId" because "robj" is null
      please follow these instructions and let me know if that doesn't resolve it for you. Evidently there is an issue with JCEF in 2025.1 under certain conditions. I will work with JetBrains via the linked issue to isolate and identify this problem, and hopefully they'll be able to provide a near-term fix.
  • Issue 2741 - Added Salesforce module import targets to the Navigate | Related Symbol list for LWC JavaScript and TypeScript files. These relationships are categorized by import type. This should hopefully provide a simple and straightforward way to navigate to other metadata being used in LWC logic. Note that this enhancement is currently only available in commercial JetBrains IDEs.
  • Issue 2781 - Fixed an issue where nested quotes would be inserted when accepting a code completion for an enumerated type LWC attribute value. Now quotes are only added if needed.
  • Issue 2783 - Fixed an issue with expression type inference for aggregate SOQL queries which can be a single AggregateResult as well as a list or array of AggregateResult.
  • Added support for displaying method separators in Apex editors. This feature can be enabled as Settings | Editor | General | Appearance | Show method separators. While the setting is called Show method separators, I have modeled the Apex behavior after the Java behavior where separators are also displayed for inner types and, specific to Apex, for property accessors with implementations.
  • Improved LWC component attribute code completion sort ordering so that first-class attributes are ordered first followed by event handlers, ARIA attributes, and directives with each subset sorted alphabetically.
  • Descriptions for standard LWC component attributes are now displayed properly in code completion lists.
  • Agentforce for Developers inline autocompletion now works in scratch files in projects with exactly one configured connection. This should hopefully provide a reasonable workaround for the IDE's inline autocompletion feature — upon which IC's Agentforce for Developers inline autocompletion integration is built — not triggering in the "lightweight" editors used in IC's Anonymous Apex, SOQL Query, and SOSL Query tool windows.
  • Other related fixes and improvements.