2.0.5.8 release notes

posted Apr 18, 2019, 10:41 AM by Scott Wells

2.0.5.8

  • Issue 1277 - Fixed an issue that could prevent scratch org creation outside of an SFDX module/project.
  • Issue 1278 - Fixed an issue that caused OST generation to fail for SFDX modules when launched from the project configuration dialog.
  • Fixed an issue that could occur when the user clicks Cancel when prompted for a scratch org definition file name while creating a scratch org. Now a temporary file is written instead.
  • Fixed an NPE that could occur during new project creation/import.

1.8.4.8 release notes

posted Apr 16, 2019, 10:36 AM by Scott Wells

1.8.4.8

  • Numerous fixes for Salesforce DX projects:
    • It is now always possible to create scratch orgs from within Illuminated Cloud, not just from the context of an SFDX project.
    • Proper handling and presentation of partial success information in SFDX push failure responses.
    • Fixed all known issues with handling of static resources in SFDX projects.
  • Fixed a boundary issue when processing PMD Apex output.
  • Added startup-time validation for the host JRE version. If an unsupported version is detected, the user is provided guidance on how to update the JRE to resolve the issue.
  • Other minor fixes and improvements.

2.0.5.7 release notes

posted Apr 16, 2019, 6:50 AM by Scott Wells

2.0.5.7

  • Issue 159 - Support for creation and use of OAuth connections in Illuminated Cloud.
    • You may now create and manage SFDX OAuth connections using a new toolbar button in IC's connection manager. IC will prompt you for a connection name, org type (optional), and login URL (optional), then will require you to log in via your Web browser. The Salesforce CLI is used for all OAuth interaction and management of the access token.
    • OAuth connections can be used anywhere that configured IC connections can be used and can be configured similarly.
    • OAuth orgs can also be used for the SFDX-develop-against-any-org feature (see below).
    • NOTE: After updating to this version or higher, each project will be upgraded upon opening to include connection type information for each usage of a connection. This ensures that there is no ambiguity when an IC connection name and a Salesforce DX alias match. If you manage your IDE configuration files in version control, please check in these changes and have your entire team, if appropriate, align on a plugin build that includes this change.
  • Issue 1184 - Support for SFDX-develop-against-any-org projects in Illuminated Cloud.
    • The Illuminated Cloud SFDX new project wizard can now create SFDX-develop-against-any-org projects by checking Generate Manifest in the first step.
    • The import project wizard automatically recognizes SFDX-develop-against-any-org projects and configures IC for them as appropriate.
    • The metadata subscription for an SFDX-develop-against-any-org project is automatically set to Package.xml and configured to use the package.xml file created during Salesforce CLI project creation. Subscription management is based mostly on manual package.xml authoring, but IC will prompt to add/remove package.xml entries as metadata files are added/removed in the IDE.
    • For the most part, SFDX-develop-against-any-org projects work exactly like IC projects using configured connections. Specifically the following features are not currently available in these types of projects:
      • Retrieve for merge is not supported because the CLI is responsible for retrieval of metadata directly into the project.
      • Namespace substitution and deployment/retrieval substitution rules are not supported for the same reason.
    • Tooling API-based deployment works for Apex classes, Visualforce pages, individual simple static resources (not bundles), and individual Aura bundle files in SFDX-develop-against-any-org projects. This can often result in much faster deployment times for these metadata types than sending them through the CLI/Metadata API.
    • Static resource bundles in these projects are managed by the Salesforce CLI.
  • Issue 852 - Added an SFDX config option to specify that all push/pull operations against scratch orgs should use the -f flag to disable conflict detection and force overwrite the target copy. This option was added for some users who are seeing consistent false conflicts reported by push and pull operations and, as a result, are having to perform the operation twice each time. NOTE: If you are not seeing this type of issue, you should not enable this config option.
  • Previously an IC SFDX project could have only one module, and it had to be an SFDX module. Now IC's SFDX support is module-oriented instead of project-oriented. This means that you may now have an IntelliJ IDEA project with multiple SFDX scratch org modules, SFDX-develop-against-any-org modules, and/or traditional username/password modules. The correct module-specific behavior should be applied at all times. NOTE: WebStorm does not support multi-module projects, so unfortunately this change only applies when IC is hosted by IntelliJ IDEA Community Edition or Ultimate Edition.
  • The logic to auto-discover IC project/modules is now much more flexible and can find one or more SFDX modules nested below the project root, potentially as peers to username/password modules, and set up the project accordingly. NOTE: WebStorm does not support multi-module projects, so unfortunately this change only applies when IC is hosted by IntelliJ IDEA Community Edition or Ultimate Edition.
  • Fixed a number of issues with static resources in SFDX projects.
  • Removed auto-added null-valued Id fields from the SOQL query results table view.
  • Added startup-time validation for the host JRE and IDE versions. If unsupported versions of either are detected, the user is provided guidance on how to update as appropriate to resolve the issue.

All Illuminated Cloud, all the time...

posted Apr 8, 2019, 10:26 AM by Scott Wells

I'm often asked whether/when IC will ever be my (only) full-time job. I'm very excited to share that, starting next week, it will be! I'm also excited that I'll finally be able to focus on some truly strategic enhancements to IC, technical and otherwise (first-class user guide!).

I'm structuring the work I'll be doing over the next several months (years?) in the wiki. For those missing them, I'll be adding an issue in the public issue tracker for each item for watching and voting. End-user feedback is always appreciated, so feel free to add your thoughts to the linked issues.

I'm REALLY looking forward to this next phase in the evolution of Illuminated Cloud!

2.0.5.6 release notes

posted Feb 15, 2019, 7:00 AM by Scott Wells

2.0.5.6
  • Issue 1165 - Metadata denoted as coming from an installed package with no namespace is now available for inclusion in subscriptions and for deployment/retrieval. This should allow users to work with metadata from unlocked packages without namespaces. Note that there will be a second change in the near future that will retain the full bodies of Apex classes denoted as such in the OST so that even if they are not included in project source, they will still be available for perusal and stepping through during offline debugging.
  • LWC deployment error reporting improvements. There are several patterns for these types of errors, and one that includes line/column number information as part of the message itself is now parsed and handled so that the exact reported location is properly linked from the error.
  • Improvements to SFDX scratch org details caching. Details should need to be reloaded much less frequently now and only when actually required.

2.0.5.5 / 1.8.4.7 release notes - Spring '19 / API v45.0 updates

posted Feb 11, 2019, 7:35 AM by Scott Wells

2.0.5.5 - Spring '19 / API v45.0 Updates

  • Updated to use an API v45.0 SOAP client and allowed API v45.0 for connections.
  • Added support for the following new language features:
    • WITH SECURITY_ENFORCED SOQL clause
    • $ContentAsset global value provider
    • $Locale global value provider date format options
    • sforce.one.showToast() JavaScript function
  • Updated the following for Spring '19 changes:
    • Aura components
    • Aura public JavaScript interfaces
    • SLDS CSS
    • SFDX scratch org features
    • Metadata XSD
    • SFDX JSON schemas
    • Integrated API documentation
  • Updated Salesforce CLI execution to expect JSON-formatted information only on stdout. Messages written to stderr are now optionally displayed in the Event Log. This can be enabled/disabled (enabled by default) in the Salesforce DX application configuration tab. When disabled, messages written to stderr are sent to idea.log only.
  • Lightning Web Components - Support for LWC was already included in official Illuminated Cloud builds. LWC support will be continuously improved in future builds.
    • Note that it is now possible to run and interactively debug Jest unit tests from within Illuminated Cloud when used with IntelliJ IDEA Ultimate Edition or WebStorm by adding "jest": ">= 23.0.0" to package.json under devDependencies. This workaround will no longer be necessary after a near-term update to IntelliJ IDEA Ultimate Edition and WebStorm.
  • NOTE: You will be prompted to regenerate the OST for each connection upon first access for changes in Spring '19 / API v45.0.
  • Issue 821 - Partial workaround: added type information for Database.DMLOptions. I will look at adding type information to other types returned from the Tooling API without it based on prevalence of use.
  • Other minor fixes and improvements.

1.8.4.7 - Spring '19 / API v45.0 Updates

  • Updated to use an API v45.0 SOAP client and allowed API v45.0 for connections.
  • Added support for the following new language features:
    • WITH SECURITY_ENFORCED SOQL clause
    • $ContentAsset global value provider
    • $Locale global value provider date format options
    • sforce.one.showToast() JavaScript function
  • Updated the following for Spring '19 changes:
    • Aura components
    • Aura public JavaScript interfaces
    • SLDS CSS
    • SFDX scratch org features
    • Metadata XSD
    • SFDX JSON schemas
    • Integrated API documentation
  • Updated Salesforce CLI execution to expect JSON-formatted information only on stdout. Messages written to stderr are now optionally displayed in the Event Log. This can be enabled/disabled (enabled by default) in the Salesforce DX application configuration tab. When disabled, messages written to stderr are sent to idea.log only.
  • Lightning Web Components - Support for LWC was already included in official Illuminated Cloud builds. LWC support will be continuously improved in future builds.
    • Note that it is now possible to run and interactively debug Jest unit tests from within Illuminated Cloud when used with IntelliJ IDEA Ultimate Edition or WebStorm by adding "jest": ">= 23.0.0" to package.json under devDependencies. This workaround will no longer be necessary after a near-term update to IntelliJ IDEA Ultimate Edition and WebStorm.
  • NOTE: You will be prompted to regenerate the OST for each connection upon first access for changes in Spring '19 / API v45.0.
  • Issue 273 - In the SOQL Query tool window, queried fields with all null values are now displayed properly.
  • Issue 821 - Partial workaround: added type information for Database.DMLOptions. I will look at adding type information to other types returned from the Tooling API without it based on prevalence of use.
  • Issue 1211 - Fixed an issue in OSTs generated against Spring '19 orgs where APEX_OBJECT would be conveyed into rendered Apex stub classes.
  • Other minor fixes and improvements.

2.0.5.3 release notes

posted Feb 5, 2019, 8:30 AM by Scott Wells

2.0.5.3

  • Issue 1046 - Fixed an issue with the plain text clipboard format for SOQL Query results. There was not a newline between the header row and the first data row.
  • Issue 1211 - Fixed an issue in OSTs generated against Spring '19 orgs where APEX_OBJECT would be conveyed into rendered Apex stub classes.
  • Issue 1216 - Added support for auxiliary HTML files in LWC components.
  • Issue 1217 - Fixed a number of bugs with the way that LWC component files are enumerated for presentation and navigation.
  • Fixed an issue with duplication of the Id field in the SOQL Query results tree view.
  • Added support for LWC service components distinct from UI components. Service components do not have HTML or CSS files, only JavaScript files. The type of a new component is specified in the New Lightning Web Component dialog (default is UI). It is not possible to add HTML or CSS files to service components.
  • Other minor fixes and improvements.

2.0.5.2 release notes

posted Jan 22, 2019, 10:59 AM by Scott Wells

2.0.5.2

  • Issue 87 - 1:M relationships are now displayed in the SOQL Query tool window. There are now two tabs, one that displays the results in tabular form as before and another that displays the results in tree form. In tabular form sub-relations are displayed as RelationshipName[index].FieldName for all results for queried sub-relations. In tree form the result set is displayed with each row from the result set as a root node and fields/sub-relations as child nodes.
  • Issue 273 - In the SOQL Query tool window, queried fields with all null values are now displayed properly.
  • Issue 1046 - The SOQL Query tool window now includes a Copy results toolbar button which copies the entire tabular result set to the clipboard as both an HTML-formatted table and tab-delimited plain text including the header row. This is also a partial response to issue 229 which requests CSV/XLS/XML export of query results as the HTML-formatted clipboard contents can be pasted into applications like Excel.

2.0.5.1 release notes

posted Jan 9, 2019, 10:44 AM by Scott Wells

2.0.5.1

  • Issue 1203 - The SFDX scratch org creation dialog now supports parameterized org features and scratch org settings. Scratch org settings are specified via a JSON block corresponding to the scratch org definition's settings key. Illuminated Cloud provides code completion for scratch org settings (currently only orgPreferenceSettings) based on Salesforce's JSON schema definition. It is still possible to use org preferences when creating scratch orgs, but note that scratch org settings and org preferences are mutually-exclusive and may not be used together in the same specification.
  • Updated the executable file extension expected on Windows from .exe to .cmd in support of the latest Windows Salesforce CLI installer.
  • Improved the IDE's behavior when the path to the Salesforce CLI executable is missing or invalid.

1.8.4.6 release notes

posted Jan 9, 2019, 10:44 AM by Scott Wells

1.8.4.6

  • Issue 1203 - The SFDX scratch org creation dialog now supports parameterized org features and scratch org settings. Scratch org settings are specified via a JSON block corresponding to the scratch org definition's settings key. It is still possible to use org preferences when creating scratch orgs, but note that scratch org settings and org preferences are mutually-exclusive and may not be used together in the same specification.
  • Updated the executable file extension expected on Windows from .exe to .cmd in support of the latest Windows Salesforce CLI installer.
  • Improved the IDE's behavior when the path to the Salesforce CLI executable is missing or invalid.

1-10 of 79