Announcements‎ > ‎

2.1.3.4 release notes

posted Aug 7, 2020, 8:02 AM by Scott Wells

2.1.3.4

  • Issue 1648 - Fixed an issue with the display of multiple child rows in the SOQL Query results tree view.
  • Issue 1674 - Added three new configuration options to the SOQL Query tool window:
    • Validate query result set size - When enabled, a count query is executed first to determine whether the number of rows returned would exceed the configured maximum query result set size. This validation is disabled by default.
    • Validate unconstrained query result set size - When enabled, a count query is executed first for unconstrained queries to determine whether the number of rows returned would exceed the configured maximum query result set size. Unconstrained queries are those with no WHERE or LIMIT clause, or those with a LIMIT clause that exceeds the configured maximum query result set size. This validation is enabled by default.
    • Maximum query result set size - The value used by the two constraints above when enabled. The value must be in the range 100-50K inclusive and defaults to 5K rows.
    All SOQL Query configuration options have also now been moved into a configuration dialog accessible from the SOQL Query tool window toolbar.
  • Issue 1684 - Fixed a deadlock observed by some users when the OAuth access token must be refreshed while enumerating all org metadata.
  • Issue 1685 - When loading an existing scratch org definition JSON file, the project's existing definition file(s) are automatically pre-selected in the file browser.
  • Fixed an issue with dynamic file type association for JavaScript-/CSS-type static resource files in metadata format projects in Community Edition IDEs.
  • Some users have encountered an issue after updating to the 2020.2 release of the base JetBrains IDE where Apex classes are no longer handled properly. This seems to be due to accidental or unintentional installation of the TeXify-IDEA plugin which also registers a file type association for the *.cls file extension pattern. Disabling or uninstalling that plugin should resolve the issue, but as of this build, Illuminated Cloud 2 detects the presence of this conflicting plugin and prompts the user to disable it.
  • Similarly, Illuminated Cloud 2 now detects when key Salesforce file type associations are not properly configured for its use, in particular those for Apex, Visualforce, Aura, and certain XML-based metadata files. When this occurs, it prompts the user to re-establish the missing file type associations. Unfortunately plugins are no longer allowed to change file type associations automatically and this must be performed manually, but Illuminated Cloud 2 clearly identifies the missing associations that should be restored.
Comments