2.1.5.2 release notes

Post date: Dec 03, 2020 2:43:17 PM

2.1.5.2

• JetBrains 2020.3 IDE compatibility - Includes updates required for proper compatibility with the 2020.3 family of JetBrains IDEs. This includes fixes/workarounds for the following regressions introduced in the new version:

  • Issue 1774 - Due to a change in the IDE's tabbed UI component, the correct tab was no longer being selected initially. This has been reported to JetBrains as IDEA-256698. Now the initial tab is selected explicitly using the EDT to ensure that it occurs after the underlying UI's own selection.

  • Issue 1775 - It seems that there is an issue with persistence of module-level configuration. This has been reported to JetBrains as IDEA-256727. Until the core issue is fixed, a workaround will be included which forces module-level configuration persistence anytime that changes are made to the underlying content.

  • Additionally support has been added for the new reader mode for ApexDoc comments. This allows you to toggle ApexDoc between and editable documentation comment and the rendered documentation. Reader mode is automatically enabled for ApexDoc comments in offline symbol table types. For more information see the Reader Mode section of the 2020.3 new feature highlights.

• Issue 1765 - Added two new Apex code formatter options under Wrapping and Braces > Keep when reformatting:

  • Simple methods in one line - Retains the formatting of an existing constructor or method that exists completely on a single line.

  • Simple classes in one line - Retains the formatting of an existing Apex class, interface, enum, or trigger that exists completely on a single line.

• Issue 1771 - Fixed an issue encountered by a user when sorting experience bundle content files for determination of the composite last modified date.

• Added Apex parser support for the SOQL keywords Mine_And_My_Groups, My_Territory, and My_Team_Territory as Apex identifier names.

• Added four new code intentions for formatting of multiple method/constructor formal parameters and invocation arguments:

  • Put arguments on one line - Puts all invocation arguments on one line.

  • Put arguments on separate lines - Puts each invocation argument on a separate line.

  • Put parameters on one line - Puts all method or constructor formal parameters on one line.

  • Put parameters on separate lines - Puts each method or constructor formal parameter on a separate line.

  • As usual, these code intentions are activated using Alt+Enter (Windows/Linux) or Opt+Enter (Mac), specifically when the caret is within a formal parameter list or invocation argument list with more than a single entry.

• Other related fixes and improvements.