Post date: May 13, 2019 3:15:7 PM
2.0.6.0
Issues 1017 / 1043 / 1064 (likely others) - Fixed all known issues with support for Salesforce DX source format project structure flexibility.
In Salesforce DX projects—either against scratch orgs or OAuth connections—it is now possible to organize your metadata as you'd like for the most part with only the few restrictions described in the linked documentation.
New metadata file creation actions are now enabled/disabled as appropriate based on the selected context when the action is initiated.
A new action for creating a new subdirectory, New>Directory, is now available as appropriate when working in source roots of Illuminated Cloud modules. Previously the standard New>Directory action was renamed to New>Package by the base IDE which is confusing for those without a Java development background.
Issue 1238 - A distinct file template is now used when creating a service Lightning Web Component.
Issue 1281 - UX improvement to the New Lightning Web Component dialog. Previously the display name was entered first and the tag/service (i.e., metadata) name and JS class name were derived from that. Now the metadata name is entered first and the JS class name and display name are derived.
UX improvement to the New Trigger dialog. Previously the SObject type selector was the first focused component. Now the trigger name field is first.
Added a new Validation and Deployment configuration option, Sort package.xml entries, which maintains the selected package.xml file's entries in proper lexicographic order as they are added and removed by Illuminated Cloud.
This option only applies to modules that use a Package.xml metadata subscription.
This option is disabled by default for backward-compatibility.
Improved the workflow experience when creating metadata. If so configured, the metadata subscription should be updated before deployment occurs therefore avoiding a prompt to deploy unsubscribed metadata.
Fixed a number of issues with handling of deleted metadata, in particular for propagation to the Salesforce organization and automatic maintenance of the metadata subscription. Bulk deletes of full directory structures should now properly infer the correct deleted metadata and handle it properly.
Fixed an issue where users would still be prompted to propagate local metadata deletes and renames in scratch org modules even when configured not to push metadata in response to those events.
Fixed an issue with missing error details from metadata delete operations.
Fixed an issue where the delete propagation dialog could be displayed when there's nothing to do.
Fixed an issue that could result in repeated deployment of a Lightning bundle when multiple files are created initially. Now only a single deployment/push should occur.
Fixed an issue where deployment of LWC bundles with Jest tests in MDAPI projects would include the Jest tests in the deployment payload, typically resulting in a failed deployment.
Fixed several issues with the copy handlers that could result in incomplete/incorrect copies, in particular for LWC bundles, static resource bundles, and static resource files in Salesforce DX modules.
Fixed all known issues with automatic metadata subscription management—both Package.xml and Selected—except for those related to support for child metadata types. Those will be addressed in the next major feature build.
Fixed an issue with tabbed editors when displaying binary static resource files.
Fixed an issue with the structure view in Visualforce/Lightning markup files that seems to have been introduced in 2019.1.
Fixed an issue with hyperlinking to deployment errors reported with a line or column number of -1.
Fixed a long-standing issue with the deploy/retrieve/delete dialog that could make all metadata seem to be local-only after a session timeout until an explicit view refresh is performed.
Removed the visibility portion of the icon for Apex types in the project view. This is consistent with how Java types are displayed in the same view in IntelliJ IDEA.
Many other fixes and overall improvements.
NOTE: The changes required for these fixes have been quite extensive. They have also been tested extensively, but it's quite possible—likely even—that regressions (hopefully minor) may have been introduced. Please report any such issues you might encounter via the public issue tracker or support email contact and they will be addressed ASAP.