1.8.5.4 release notes

posted by Scott Wells

1.8.5.4 - Winter '20 / API v47.0 Update

  • Updated SOAP clients from API v47.0 WSDLs.
  • Updated the internal API version to 47.0.
  • Added 47.0 as an explicitly-selectable API version in the connection manager.
  • Added support for the $MessageChannel Visualforce global variable and lightning:messageChannel Aura component.
  • Added Winter '20 scratch org features for use in the scratch org creation dialog.
  • Updated the bundled SLDS CSS to 2.10.0.
  • Updated metadata.xsd to v47.0 for code completion and validation in XML metadata files.
  • Updated all bundled API documentation.
  • Other minor changes and improvements.

2.0.8.9 release notes

posted by Scott Wells

2.0.8.9 - Winter '20 / API v47.0 Update

  • Updated SOAP clients from API v47.0 WSDLs.
  • Updated the internal API version to 47.0.
  • Added 47.0 as an explicitly-selectable API version in the connection manager.
  • Updated all LWC standard components for code completion and validation.
  • Added support for the $MessageChannel Visualforce global variable and lightning:messageChannel Aura component.
  • Added Winter '20 scratch org features for use in the scratch org creation dialog.
  • Updated the Salesforce DX JSON schema files for sfdx-project.json and *-scratch-def.json code completion and validation.
  • Updated the bundled SLDS CSS to 2.10.0.
  • Updated metadata.xsd to v47.0 for code completion and validation in XML metadata files.
  • Updated all bundled API documentation.
  • Incremented the OST version number to prompt users to update their OSTs for Winter '20 changes.
  • Other minor changes and improvements.

2.0.8.8 release notes

posted Oct 9, 2019, 11:13 AM by Scott Wells   [ updated Oct 9, 2019, 11:14 AM ]

2.0.8.8
  • Issue 1444 - Fixed an issue when deploying LWC components with tests in a traditional module.

2.0.8.7 release notes

posted Oct 8, 2019, 9:30 AM by Scott Wells

2.0.8.7

  • Issue 876 / Issue 1404 - The user is now prompted when attempting to execute an unconstrained SOQL query (no WHERE or LIMIT clauses) that includes Blob-type fields and/or sub-queries. These types of queries can result in very large result sets that are slow to execute, transfer, and/or process. This behavior is configurable via the new settings drop-down on the SOQL Query toolbar (both enabled by default).
  • Issue 1433 - Fixed an issue with incorrect handling of rollback-on-error when deploying to an organization that does not allow partial saves (typically production organizations).
  • Log Analyzer performance improvements when opening moderate-to-large-sized logs in the tree table view. There is one other optimization that I'm currently investigating and, if it proves worthwhile, will include in another near-term release.
  • Improved progress reporting when loading very large numbers of users and/or Apex classes/triggers for trace flag creation.

Lightning Web Components local development with Illuminated Cloud (Beta)

posted Oct 3, 2019, 10:06 AM by Scott Wells   [ updated Oct 11, 2019, 6:39 AM ]

The beta for local development of Lightning Web Components is now available! This post describes how to use Illuminated Cloud with the LWC local development server.

CLI Installation

This post provides condensed instructions for installing, configuring, and using the LWC local dev server with Illuminated Cloud. For full details, please see the official documentation.

Make sure that the Salesforce CLI is up-to-date:

$ sfdx update

Install the LWC local dev server plugin:

$ sfdx plugins:install @salesforce/lwc-dev-server

Server Startup

From a project directory, start the LWC local dev server:

$ sfdx force:lightning:lwc:start -u <usernameOrAlias> [-p <port>]

The default value for <port> if unspecified is 3333.

NOTE: A new instance of the server must be started for each project. You can either stop the running server using Ctrl+C before starting a new instance in another project, or you must specify a unique port for each new instance. For the sake of simplicity and efficiency, I recommend that you only have a single dev server instance running at any given time.

Open http://localhost:<port>/ (again, the default port is 3333) in a browser to access the local dev server. You will be presented a list of components from the local project. Click any component to view and work with that component.

IDE Configuration

If not already so, open the Illuminated Cloud project from which the LWC local dev server was started.

In the Illuminated Cloud Project view, right-click on the .localdevserver node and click Mark Directory as>Excluded. This is only necessary once per-project and will ensure that Illuminated Cloud does not attempt to include the local dev server's working files in the project.

Development

While working in local dev server mode, it is recommended that you temporarily disable deploy-on-save in application settings. For traditional projects and SFDX-dev-against-any-org projects, you can do this under Validation and Deployment settings. For scratch org projects, you can do this under Salesforce DX settings.

Now when you save changes to an LWC component in Illuminated Cloud, the LWC local dev server will automatically pick up the changes, recompile the component, and instruct the browser to refresh if appropriate.

Debugging

To debug your components, use the browser's development tools. Compiled component source can be found under:

localhost:<port>/
  webruntime/
    component/
      <id>/dev/<locale>/<namespace>/
        <camelCasedComponentName>.js

Future IDE Integration

In a near-term update to Illuminated Cloud I plan to add the following first-class features for LWC local development:
  • Action to start the LWC local dev server with the project connection's user and a unique port.
  • Action to open a selected LWC component in the LWC local dev server, starting it first if necessary.
  • Automatic exclusion of the .localdevserver directory.
  • Automatic suppression of deploy-on-save for LWC components while working against an LWC local dev server.
Salesforce will also be allowing external tools to customize the way that source code links are handled. Once that extension point is available, you will be able to navigate from the browser back into the corresponding source in Illuminated Cloud.

Once Salesforce includes source maps for compiled LWC components, I'll look into fully-integrated IDE-based debugging of LWC components rendered in the browser.

2.0.8.6 release notes

posted Oct 3, 2019, 8:32 AM by Scott Wells

2.0.8.6

  • Issue 320 - It's now possible to specify that unit tests be executed during deployment and exactly which tests should be included. The bulk deployment dialog includes a test level selector with all valid test levels. If no test level is selected, the default test-on-deploy behavior occurs based on the target organization. If Run Specified Tests is selected, the user is able to choose an Apex unit test run configuration to designate the subset of unit tests to be executed during deployment. Unit test failures are displayed in the Messages and Illuminated Cloud Problems views hyperlinked to the associated source files when possible.
    • NOTE: Due to a bug in the Salesforce CLI, test execution results are not displayed when deploying via force:source:deploy. This bug has been reported to Salesforce and, once it is resolved, test execution results should be displayed properly. This bug only affects commit deployments; check-only deployments via force:source:deploy properly include test execution details.
  • Issue 408 - It's now possible to designate any bulk deployment as check-only so that the selected metadata is validated but not committed to the target organization. The bulk deployment dialog includes a Check Only option which, when checked, causes the deployment to be treated as a check-only operation.
  • Issue 1262 - It's now possible to specify the exact behavior of bulk deployments and deletes including how errors and warnings should be treated. Traditionally Illuminated Cloud has specified that deployments should ignore errors and warnings, and this is still the default behavior, but there are now Ignore Errors and Ignore Warnings options in the bulk deployment and delete dialogs that, when unchecked, cause the entire deployment operation to roll back when any errors or warnings occur. Bulk delete operations also include a Purge on Delete option to determine whether deleted metadata should be moved to the recycle bin (unchecked) or completely removed from the target organization (checked / default).
    • Options which are not allowed for the target organization are disabled for configuration, e.g., errors cannot be ignored when deploying to a production organization.
    • Illuminated Cloud determines that a connection is for a production organization as follows:
      1. If the Use Salesforce-reported organization type setting is checked in the Validation and Deployment screen, the Salesforce API is used to determine the organization type.
      2. If the Use Salesforce-reported organization type setting is unchecked in the Validation and Deployment screen, the connection's Organization type setting is used.
  • All of these configuration settings are remembered and restored across subsequent bulk operations for each given connection.
  • Other fixes and improvements.

2.0.8.5 release notes

posted Sep 27, 2019, 10:31 AM by Scott Wells

2.0.8.5

  • Issue 702 - Added full first-class support for Wave metadata. Wave metadata is a bit different in that most of the metadata types for Wave share the same metadata type folder, wave. Wave template bundles are also handled similar to Lightning bundles and static resource bundles.
  • Issue 1424 - Fixed a few issues with prompting on deployment of unsubscribed metadata. An issue was introduced in 2.0.8.3/2.0.8.4 with custom labels when subscribing as CustomLabels vs. CustomLabel. That should be fixed now, and you're also properly prompted when deploying single Aura bundle files and single static resources via the Tooling API.
  • Issue 1428 - Fixed an issue that could occur when clicking the log configuration button with no connection selected. Now a connection must be selected for that action to be enabled.
  • Added the dev hub org ID to the connection details for scratch orgs in the connection manager.
  • A test level is now always specified for deployments via the metadata API, whether using IC's native deployer or force:source:deploy. Deployments to production organizations currently specify RunLocalTests, and all other deployments currently specify NoTestRun.
    • NOTE: Due to a bug in force:source:deploy, test execution status is not properly reported when tests are run during deployment and the --json option is used. I have reported this to Salesforce and hopefully it will be resolved soon.
  • Fixed an issue that could occur when resolving a line number from a unit test failure that is outside the range of lines in the associated file.
  • Fixed the annoying log warning about an invalid shortcut key for compare-with-server.
  • Several other fixes and improvements.

2.0.8.4 release notes

posted Sep 20, 2019, 8:24 AM by Scott Wells

2.0.8.4

  • Issue 1405 - It's now possible to specify that a scratch org should be created as Preview or Previous (relative to the dev hub) during the pre-release window.
  • Issue 1417 - Made the traced entity queries for Apex classes/triggers and users batch properly so that all potential values are available for selection.
  • Issue 1422 - Reverted a 2.0.8.3 change that could result in a runtime error due to an incompatible plugin SDK change for users in 2019.1 or earlier.
  • Fixed a cosmetic issue in the Log Analyzer tree table view when the editor font size is increased.
  • Restored IC1/IC2 plugin conflict detection which had been broken by a recent base IDE change. Now if both the IC1 and IC2 plugins are installed and enabled, the user will be prompted to select which one should remain enabled and IC will make the appropriate plugin configuration changes.

2.0.8.3 release notes

posted Sep 18, 2019, 10:59 AM by Scott Wells

2.0.8.3

  • Issue 788 / Issue 1035 / Issue 1067 / Issue 1283 / likely others - Illuminated Cloud now handles child metadata types properly during metadata deployment/retrieval/delete and metadata subscription management:
    • It is now possible to deploy, retrieve, or delete specific child metadata objects without being required to transfer the entire containing file. Previously this was possible in Salesforce DX dev-against-any-org modules for decomposed metadata and to a limited extent in all non-scratch org modules for retrieval and delete. It should now work properly in all non-scratch org modules (and even in scratch org modules using raw deploy/retrieve/delete actions) and for all composite metadata types.
      • NOTE: - Errors reported for selective deployment of child metadata objects may include line numbers which do not correspond to the original source files due to the selective extraction of child metadata XML elements.
    • Child metadata in the deploy/retrieve/delete dialog is now displayed directly beneath the corresponding parent metadata in child metadata type-specific sub-folders.
    • The deploy/retrieve/delete dialog now clearly identifies child metadata that is included in the subscription implicitly by inclusion of its parent metadata (Subscribed by Parent) and unsubscribed parent metadata that is displayed because of subscribed children (Included by Child). The former can be filtered out of the dialog if desired using the corresponding filter checkbox.
    • When creating a custom metadata selection in the deploy/retrieve/delete dialog, selection of unsubscribed metadata shows temporarily subscribed by explicit selection to identify one-off selections clearly.
    • The Add to Metadata Subscription action now properly processes composite metadata files. If a file contains both parent- and child-level customizations, only the parent is added to the subscription; if the file contains only child-level customizations, only the specific children are added. If children are added to a subscription which already includes the parent explicitly or via wildcard, no changes are made.
  • Issue 268 - Added a first-class Compare With Server action (previously available only in the deploy/retrieve/delete dialog). This new action is available on the toolbar, drop-down menu, and context menu as well as via the keyboard shortcut Ctrl+Alt+Shift+= on Windows/Linux and Cmd+Opt+Shift+= on Mac. This action retrieves server copies of all locally-selected metadata (recursively) for display in the IDE's configured diff tool.
  • Made the Compare With Server action in the deploy/retrieve/delete dialog support multiple selections. If an unsubscribed parent metadata object is requested for comparison, the user is now prompted whether to compare only the subscribed children of that parent or against the full parent object.
  • Added support for as-you-type validation in Salesforce DX dev-against-any-org modules. When possible Illuminated Cloud will use the Tooling API for check-only deployments, but when a Tooling API deployment option is not available be aware that check-only deployments via the Salesforce CLI can be quite slow at present resulting in potential lag before validation results are available.
  • Issue 1414 - Fixed an OST generation issue with custom metadata type fields that are references to entity definitions and field definitions. Previously these fields would be rendered into the OST as String-valued properties with no corresponding relationship properties. Now they are properly rendered as an Id and EntityDefinition/FieldDefinition relationship pair.
    • NOTE: You must regenerate your OST (at least the SObjects) for this fix to take effect.
  • Fixed an OST generation issue where the UserRecordAccess field was missing.
    • NOTE: You must regenerate your OST (at least the SObjects) for this fix to take effect.
  • Fixed a number of issues with metadata management, particularly in Salesforce DX dev-against-any-org modules.
  • Other fixes and improvements.

2.0.7.9 release notes

posted Aug 23, 2019, 6:27 AM by Scott Wells

2.0.7.9

  • Issue 969 - Illuminated Cloud now includes a status bar widget that displays the configured connection for the current file similar to the version control branch status bar widget. When clicked, all connections which are valid for the current file's module are displayed, and the following actions are available for each connection:
    • Set as connection for <module> - Switches the module containing the current file to use the selected connection. If more than one module uses the current configured connection, the user is prompted whether to update just the current file's module or all modules that use that connection. Not available for the current configured connection.
    • Open connection... - Opens the selected connection in a Web browser.
    • Edit connection... - Opens the connection manager for the selected connection.
    Note that this is not intended to be a replacement for the Open connection toolbar drop-down. This view only shows connections which are valid for the current file's module and not all configured connections. See below for a usability enhancement to the Open connection feature that's also in this build.
  • Added a keyboard shortcut for Open connectionCtrl+Alt+Shift+O on Windows/Linux and Cmd+Opt+Shift+O on Mac. A searchable/filterable list of all configured connections is displayed.
  • Added the username to the traced entity selector when creating a trace flag for a user.
  • Made the new log configuration dialog's traced entity selector searchable/filterable. Type the partial name/username of a user or name/namespace of an Apex class/trigger to filter the list for simplified selection.
  • Other minor fixes and improvements.

1-10 of 113