2.3.0.9 release notes

2.3.0.9

  • Issue 1245 - Added missing Aura component attributes lightning:accordionSection > label and aura:handler > includeFacets.
  • Issue 1886 - Fixed an issue with Apex parser recovery in ternary expressions when there are syntax errors in the second (i.e., true branch) expression.
  • Issue 1991 - Fixed an issue with the Apex lexer incorrectly tokenizing /**/ as an unterminated documentation comment.
  • Issue 1992 - Fixed an issue with Apex parser pinning and recovery when an inner interface is followed by a member variable without annotations or modifiers.
  • Issue 2554 - Fixed an issue that would prevent the connection status bar widget from displaying when no Salesforce CLI is found by or registered with IC2.
  • Issue 2555 - Added copy-to-clipboard support for SOQL query results in the tree view (in addition to existing copy support for the table view) as JSON, both plain text and syntax-highlighted HTML data flavors.
  • Fixed an issue with Mermaid-based Flow diagram markup when the experimental Elk renderer is used.

JetBrains 2024.1 Known Issues

I wanted to make users aware of two known regressions in the JetBrains 2024.1 releases. Both regressions have been logged with JetBrains, reproduced successfully, and apparently already have fixes committed for near-term patches:
  • Issue 2551 - The Inconsistent API Version code inspection's file-level banner can end up being added multiple times. The corresponding entry in JetBrains' issue tracker is IJPL-995.
  • Issue 2553 - When using the Retrieve for Merge action with the native JetBrains directory diff tool and copying files from left to right, files can be added to an incorrect directory, e.g., srcclasses instead of src/classes. The corresponding entry in JetBrains' issue tracker is IJPL-148470 (which has itself been merged as a duplicate of IJPL-99511).

Public Issue Tracker Cleanup

This week I've also made a full (and long overdue) grooming/cleanup pass on the IC2 public issue tracker, resolving old issues that were either fixed or had become inactive over time, merging duplicate issues, moving remaining issues into the appropriate components, and updating issue titles & descriptions for clarity. You may have even seen one or more of your own logged issues moved into a resolved state. If so, and if they're still issues, feel free to reopen them, but please also include fresh diagnostic information and/or steps to reproduce so that they're properly actionable.

With this cleanup pass, the issue tracker once against represents a useful backlog for future work. My plan is to try to organize that work into "themes" based on related issues — both enhancements and bugs — from the various components. Of course, bugs and other critical items will be addressed as needed in conjunction with those theme-based releases. For example, in this build I addressed a number of Apex lexer/parser issues as the central theme, but I also addressed some bugs from recent updates to both IC2 and its dependencies such as the JetBrains 2024.1 releases and the Mermaid plugin.

And of course, please weigh in on items in the issue tracker with your own votes as I definitely use that as input for prioritization of future work (alongside a number of other key inputs).