2.4.1.8 release notes

2.4.1.8

  • Issue 2957 - Fixed an issue where errors could occur when adding/removing Apex offline debugger server-side checkpoints.
  • 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.
  • 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.
  • 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.
  • 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.
  • Fixed an issue with the LSP4IJ DAP-based aer debugger not stopping on breakpoints properly.
  • 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.