Skip to main content
2.3.9.0 release notes
2.3.9.0
- Implemented several fixes and improvements for the Apex offline debugger:
- Issue 2899 - Fixed a potential
AbstractMethodError during offline Apex debugging due to a breaking plugin SDK change. - Issue 2900 - Added recovery for some instances of unbalanced stack frames found in Apex debug logs. This issue has been reported to Salesforce so that it can be fixed properly, but hopefully this recovery mechanism will allow logs with such issues to be used properly.
- Fixed a few issues with the Step Out action so that it should no longer execute the rest of the process when trying to step out of a single method.
- Improved Smart Step Into functionality, particularly how it determines which invokables should be offered for the current statement.
- Debugger variables are now sorted by last modified descending by default so that the most recently-changed variables appear at the top of the list. This is more in line with how JetBrains' debuggers for other languages work. If you prefer the original alphabetic ordering, you can re-enable it using ⋮ | Debugger Settings | Sort Variables Alphabetically in the IDE debugger UI.
- Issue 2901 - Fixed an issue with expression type inference with two primitive type operands of different but assignable types.
- Added an inheritance relationship between
QuickAction.SendEmailQuickActionDefaults and QuickAction.QuickActionDefaults. The OST must be regenerated to see the effect of this fix. - Improved presentation and filtering of Apex
switch statement SObject type code completions. - Changed the
lwc_types and graphql_schema libraries to be of type Provided instead of Compile. Existing libraries aren't updated — nor do they need to be — but any new libraries created by IC will be of this corrected type. - Fixed an issue with IC-assisted enablement of the Cline plugin on Windows/ARM64.
- Removed bundled licensing software support for x86 (32-bit) on Windows and Linux. I can't imagine that anyone was still using IC with a 32-bit CPU, but if this has caused you issues, please let me know and I can restore it. Otherwise it helps slim down the plugin distribution a bit by removing (presumably) completely unused artifacts.