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.8.4.5 / 2.0.5.0 release notes

posted Jan 4, 2019, 10:08 AM by Scott Wells

1.8.4.5 / 2.0.5.0

  • Issue 654 - Further updated so that @IsTest-annotated methods in non-test classes are properly recognized.
  • Issue 1199 - Partial fix for unnecessary/incorrect language injection in comments.
  • Issue 1203 - Partial fix. Added missing simple SFDX features. Full fix coming in the next build with support for parameterized features and org settings.
  • Issue 1205 - Added missing lightning:inputField > disabled attribute.

1.8.4.4 / 2.0.4.9 release notes

posted Jan 2, 2019, 6:30 AM by Scott Wells

1.8.4.4 / 2.0.4.9

  • Issue 654 - Old-style test methods--those with the testMethod modifier in classes without an @IsTest annotation--should now work properly.
  • Issue 1200 - Added a workaround for an issue with layouts from managed packages where the API names are reported as Type_Name-Layout_Name instead of Type_Name-Namespace__Layout_Name.
  • Issue 1202 - Fixed the data type for aura:set > value.
  • Another update for Flow behavior changes in API v44.0 and higher. Hopefully this time everything works properly both pre-v44.0 and v44.0+.
  • Another fix for {!..} expressions in Visualforce that weren't being handled properly after a recent base IDE change.

2.0.4.8 release notes

posted Dec 16, 2018, 4:39 PM by Scott Wells

2.0.4.8

  • More licensing behavior improvements on/around license expiration/subscription renewal boundaries.
Note that I've also updated the Support page with information for those encountering inactive license issues on the same day as their subscription renewal.

2.0.4.7 release notes

posted Dec 15, 2018, 10:18 AM by Scott Wells

2.0.4.7

  • Fixed a few small LWC issues including suppression of errors/warnings for if:*for:*, and iterator:* attributes in LWC markup.
  • Updated the LWC system component library to the latest-and-greatest.
  • Licensing behavior improvements on/around license expiration/subscription renewal boundaries.

1-10 of 75