2.1.4.0 release notes

posted Sep 17, 2020, 10:48 AM by Scott Wells

2.1.4.0

  • Issues 1140 and 1413 (partial) - Illuminated Cloud now automatically sets the CLI's default username when an OAuth or scratch org connection is associated with an IC module. For existing projects, IC will inform the user when the CLI's default username is not configured properly or at all and will assist in setting the CLI's default username accordingly. This behavior is enabled by default but can be disabled if desired in Illuminated Cloud > Configure Application > Salesforce DX by unchecking Automatically set default username.
  • Issue 1693 - Implemented a performance optimization in the LWC HTML editor when referencing custom components.
  • Issue 1702 - Implemented a performance optimization in the build options dialog that could result in a seeming freeze when switching views.
  • Issue 1709 - Fixed an issue with the SOQL Query tool window's row count validation when trying to execute a COUNT query.
  • Issue 1711 (partial) - Updated the definition of NodeSelector to be more accurate.
  • Provided a workaround for Salesforce CLI issue 482 where dev hub orgs are sometimes not reported as such by force:org:list. If you are experiencing this issue, you can now explicitly designate an OAuth connection as a dev hub using Treat as dev hub which and that org will become available for scratch org creation. If the CLI does not report any orgs as dev hubs and none are enabled using this workaround, Illuminated Cloud will now inform the user of the workaround when the user attempts to create a scratch org.
  • Fixed several issues with quick documentation for custom labels.
  • Other minor fixes and improvements.

2.1.3.9 release notes

posted Sep 10, 2020, 7:13 AM by Scott Wells

2.1.3.9

  • Salesforce CLI connection improvements
    • IMPORTANT: Please ensure that your Salesforce CLI is up-to-date as, beginning with this update, Illuminated Cloud uses the --skipconnectionstatus argument of the force:org:list command unconditionally.
    • The behavior when cached CLI connection list and detail information appears to be stale can now be configured:
      • Connection list behavior options
        • Refresh (default) - Immediately and synchronously runs sfdx force:org:list --skipconnectionstatus to repopulate the connection list cache. This can be (significantly) faster but can yield stale connection status information.
        • Force Refresh - Immediately and synchronously runs sfdx force:org:list to repopulate the connection list cache. This can be (significantly) slower but yields accurate connection status information.
        • Notify - Displays a stale cache notification to the end user with options to refresh, force refresh, defer the notification, or configure the stale cache behavior.
        • Do Nothing - No action is taken. The user is responsible for maintaining the connection cache via the connection manager and/or named actions.
      • Connection details behavior options
        • Refresh (default) - Immediately and synchronously runs sfdx force:org:display to repopulate the connection details cache for the specific connection.
        • Notify - Displays a stale cache notification to the end user with options to refresh, defer the notification, or configure the stale cache behavior.
        • Do Nothing - No action is taken. The user is responsible for maintaining the connection cache via the connection manager and/or named actions.
    • Connection manager toolbar button changes and additions for Salesforce CLI connections:
      • Refresh (changed) - Runs sfdx force:org:list --skipconnectionstatus to repopulate the connection list cache. This can be (significantly) faster but can yield stale connection status information.
      • Force Refresh (added) - Runs sfdx force:org:list to repopulate the connection list cache. This can be (significantly) slower but yields accurate connection status information.
      • Remove Stale (added) - Runs sfdx force:org:list --clean --noprompt to remove stale/expired scratch org entries. This should be run occasionally to ensure that the performance of sfdx force:org:list does not degrade over time due to stale/expired scratch orgs.
    • All internal requests to refresh the Salesforce CLI connection list—except those in response to a detected stale cache—are now executed with the --skipconnectionstatus argument.
    • More extensive status information for Salesforce CLI connections:
      • Scratch org expiration dates are displayed prominently. Expired scratch orgs are highlighted as errors.
      • OAuth orgs with an invalid connection status are highlighted as errors. NOTE: Only a Force Refresh of the Salesforce CLI connection list includes accurate connection status information.
      • Tooltips (displayed on mouse hover) now include org status information reported by the CLI.
  • Issue 1666 - Made the default button in the write confirmation prompt configurable. When write confirmation is enabled, the user can specify the default button to be Yes (default), No, or Same as last response. If Same as last response is specified, the default button is the same as the one selected for the previous write confirmation.
  • Issue 1705 - NodeSelector is now properly represented in the core LWC libs.
  • Other minor fixes and improvements.

2.1.3.8 release notes

posted Sep 3, 2020, 8:28 AM by Scott Wells   [ updated Sep 3, 2020, 8:28 AM ]

2.1.3.8

  • Issue 274 - Enabled several new code folding regions including all code blocks, inline SOQL and SOSL queries, and collection initializers. Added support for custom code folding regions.
  • Issue 1698 - The SOQL Query tool window now supports exporting of query result sets to CSV files via a new Export action located immediately below the Execute action on the toolbar.
  • Issue 1701 - Fixed an issue with SOQL query execution against certain system SObjects that don't support the COUNT aggregate, specifically UserRecordAccess.
  • Issue 1702 - Implemented several prospective fixes/improvements for an issue observed by a few users in the build options dialog and metadata subscription editor. It's unlikely that this is completely fixed, but hopefully these fixes and improvements will help with the situation.
  • Issue 1703 - Added the Sfc namespace types to the OST as these are missing from the Salesforce Tooling API's Apex completions REST resource. To see the effect of this change, the OST must be regenerated.
  • Other minor fixes and improvements.

2.1.3.7 release notes

posted Aug 27, 2020, 8:28 AM by Scott Wells

2.1.3.7

  • Issue 1554 (redux) - It's now possible to configure the Apex source file size above which real-time Apex code inspections become inactive. The default value is still 500K bytes, and the value can be configured to any value between 50K and 2MM bytes. The value is configured directly via the file-level annotation that is added to files above this threshold.

    Related to this change, a workaround has been implemented for IDEA-249095 which results in multiple file-level annotations being displayed when tabbed editors are used. Until that issue is fixed, Apex source files above the configured threshold will not be displayed in tabbed editors. The associated meta.xml files can still be opened either directly using the Navigate > File... action or from the corresponding Apex source file using the Navigate > Related Symbol... action.

  • Issue 1696 - Made System.StaticResourceCalloutMock and System.MultiStaticResourceCalloutMock properly implement System.HttpCalloutMock. To see the results of this change, the OST must be regenerated.
  • Issue 1697 - Fixed a regression introduced by 2.1.3.6 with autocompletion of Visualforce system component attributes.
  • Illuminated Cloud tabs in the Messages tool window can now be pinned. When pinned, a tab's contents will not be replaced when the associated operation is repeated. This is useful, for example, if a deployment fails with many errors and you'd like to retain the full error list while repeating the same or a subset of the failed deployment. To pin a tab, right-click on the tab header and click Pin Tab.
  • Illuminated Cloud tabs in the Messages tool window now display operation-specific icons.
  • Added an Update now link to the metadata cache status label displayed in the build options dialog and metadata subscription editor. This performs the exact same operation as the corresponding Refresh toolbar buttons, but it provides a more immediate cue to the user as to how the cache can be updated to reflect the latest organization metadata.
  • Other minor fixes and improvements.

2.1.3.6 release notes

posted Aug 21, 2020, 8:26 AM by Scott Wells

2.1.3.6

  • Issue 482 - Fixed all known issues with aliases in SOQL queries.
  • Issue 1554 - Fixed a number of issues with large Apex source files. This includes an index optimization that should also yield improvements on even moderately-sized source files and automatic disabling of Apex code inspections in files over 500K in size.
  • Issue 1687 - You can now double-click or right-click on ID-type values in the SOQL Query tool window table and tree views to open the associated object in Salesforce via the browser.
  • Block comments are now handled properly in the SOQL Query tool window.
  • Fixed some Salesforce API quick documentation formatting issues that occur in more recent JetBrains IDEs.
  • Other minor fixes and improvements.

2.1.3.5 release notes

posted Aug 12, 2020, 8:32 AM by Scott Wells

2.1.3.5

  • Issue 1676 - Added support for push/pull against source-tracked sandboxes. To enable this behavior for a sandbox, check Use push/pull instead of deploy/retrieve/delete in the sandbox org's connection settings. When enabled, the sandbox will behave exactly like a scratch org with push and pull as the default behavior for metadata operations (including deploy-on-save) and raw deploy/retrieve/delete operations available as explicitly-invoked actions. The environment variable SFDX_ENABLE_MULTIUDX is automatically set to true for all push/pull operations against source-tracked sandboxes.
  • Similarly, added support for deploy/retrieve/delete as the optional default behavior against scratch orgs. To enable this behavior for a scratch org, check Use push/pull instead of deploy/retrieve/delete in the scratch org's connection settings. When enabled, the scratch will behave exactly like an OAuth org with raw deploy/retrieve/delete as the default behavior for metadata operations (including deploy-on-save).
  • Removed the Salesforce DX > Allow deploy/retrieve/delete operations against scratch orgs configuration option. That behavior is now always enabled.

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.

2.1.3.3 release notes

posted Jul 28, 2020, 9:04 PM by Scott Wells

2.1.3.3

  • Updates for JetBrains 2020.2 - This update includes changes required for Illuminated Cloud 2 to work with the 2020.2 IDE releases.

2.1.3.2 release notes

posted Jul 23, 2020, 11:01 AM by Scott Wells

2.1.3.2

  • Lightning Message Service Support Improvements
    • Added support for code completion and reference navigation in the type attribute of the lightning:messageChannel Aura component.
    • Added full support for importing message channels using a new LWC ES6 live template:
      • importchannel - Imports a message channel as import <alias> from '@salesforce/messageChannel/<channel>';
    • When a message channel metadata file is renamed, all Visualforce, Aura, and LWC references are updated accordingly.
    • Fixed an issue with deployment error reporting for *.messageChannel[-meta.xml] files.
  • Other related fixes and improvements.

2.1.3.1 release notes

posted Jul 20, 2020, 8:05 AM by Scott Wells

2.1.3.1

  • Summer '20 / API v49.0 Updates
    • Updated the SOAP client to be based on API v49.0 WSDLs.
    • Updated the API version used for primary communication with Salesforce APIs to 49.0.
    • Added 49.0 as an available API version number for configured connections.
    • Updated the OST version number to prompt regeneration for changes in API v49.0.
    • Updated the metadata.xsd used for validation and completion in XML metadata files for Summer '20.
    • Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '20.
    • Updated Visualforce, Aura, and LWC for the GA release of Lightning Message Service.
    • Added full support for the new @JsonAccess annotation.
    • Added full support LWC style components which include only a CSS file and a corresponding meta.xml file. It's now possible to create style components in the LWC new component wizard, and there is full support for importing style components using CSS including a new LWC CSS-specific live template:
      • import - Imports an external stylesheet or style component as @import '<stylesheetOrComponent>';.
    • Added full support for LWC user/custom permission imports. This includes the following two new LWC import live templates:
      • importpermu - Imports a standard user permission as import <alias> from '@salesforce/userPermission/<permission>';
      • importpermc - Imports a custom permission as import <alias> from '@salesforce/customPermission/<permission>';
    • Added support for ES6 properties with names that begin with an upper-cased character. The kebab-cased translation is prefixed with a leading -.
    • Updated the available editions when creating a scratch org to include the Partner values.
    • Updated the JSON schema for sfdx-project.json.
    • Updated the JSON schema for project-scratch-def.json. I also made a full pass on the various settings objects that can be configured to provide as complete and accurate of code completion and validation as possible given current information. NOTE: The JSON schema for these settings objects are not documented, and some of the composite types are not 100% correct in the current implementation. I have raised this lack of documentation with Salesforce and we are collaborating on correcting this. I will update the schema as appropriate as new information is available, but if you see an issue with code completion and/or validation relative to what you know it should be, please let me know and I'll also correct it based on that type of input.
    • Updated the bundled SLDS to 2.12.2 (sanitized version).
    • Updated the standard value set names.
    • Updated all integrated API documentation.
  • Issue 1671 - The Salesforce CLI sometimes doesn't report a dev hub org as such, though it does designate it as the org with the default dev hub username if so configured. I've filed an issue against the CLI for this, but I've also updated Illuminated Cloud to infer the former from the latter when this situation exists.
  • Other related fixes and improvements.

1-10 of 165