Illuminated Cloud 2 birthday and subscription renewals

posted by Scott Wells

Illuminated Cloud 2 turns one year old today! That also means that subscriptions are starting to renew. Over the past several weeks/months I've implemented some UX improvements for integrated IC's licensing, so please update to the latest version for the smoothest experience. It should just prompt you to re-verify your license once. Needless to say, if you have any issues let me know ASAP and I'll take care of them.

Thanks much for an amazing year!
Scott

2.0.4.6 release notes

posted Dec 13, 2018, 12:38 PM by Scott Wells

2.0.4.6

  • Issues 1193 - Updated for some Spring '19 changes including the metadata type dir being lwc instead of lightningcomponents and custom component names being likeThis instead of like_this. Also corrected the default imports in JavaScript file templates.

2.0.4.5 release notes (LWC beta support)

posted Dec 13, 2018, 7:20 AM by Scott Wells

2.0.4.5

  • Lightning Web Components (LWC) Support (beta)

    Note that you must also have access to an LWC-enabled early access organization until the feature is released for general-availability

    • Implemented
      • LWC development in both traditional/MDAPI and Salesforce DX projects
      • Code completion for standard and custom LWC components and their attributes
      • Reference injection/navigation for usages of ES6 properties and methods in template markup braced expressions
      • Integrated documentation for standard and custom LWC components and their attributes
      • Tabbed editor support for LWC bundle files
      • Tight integration with IntelliJ IDEA Ultimate Edition and WebStorm ES6 editor capabilities including:
        • Web Components template markup support
        • NPM-based dependency resolution - right-click on package.json and choose Run 'npm install' to instruct the IDE to resolve all NPM dependencies
        • Multi-language refactoring capabilities - renaming an ES6 property or method will update references in template markup braced expressions
      • File template-based creation of LWC components and supporting files:
        • Template markup
        • Component ES6 class/module
        • CSS style
        • meta.xml file
        • ES6 support/helper classes
        • Jest tests
    • Not Yet Implemented / Known Issues
      • ES6+ support in IntelliJ IDEA Community Edition (CE). The limited support for JavaScript and CSS in CE is provided by a JavaScript parser without ES6+ support and with no knowledge of technologies such as NPM. As a result, JavaScript features in CE will be very limited relative to the experience offered by IntelliJ IDEA Ultimate Edition (UE) and WebStorm (WS) which include JetBrains' full HTML5/JavaScript/CSS editors and framework support. While I may look for an alternative JavaScript parser to provide better ES6 handling in CE, the LWC experience will always be dramatically better when using IC with either UE or WS.
      • Proper handling of special import...from '@salesforce/* directives in ES6 files. This will be be addressed shortly.
      • Code completion for component attributes with constrained/enumerated values. This information is not yet available in Salesforce's standard component definitions.
      • Some valid attributes of system components are also missing from Salesforce's standard component definitions and will therefore not be offered as code completions until those omissions are addressed.
      • Fully-integrated Jest testing. IntelliJ IDEA Ultimate Edition and WebStorm provide first-class support for Jest test execution. However, currently there is some configuration/context that must be provided to the test runner for LWC Jest tests to execute successfully. I will be working with Salesforce to resolve this issue so that Jest tests can be executed in a first-class manner. In the interim, it is possible to execute Jest tests from the npmtool window (right-click on package.json and choose Show npm scripts, then double-click test:unit).
      • Tooling API-based deployment of LWC bundle files in traditional/MDAPI projects. There doesn't appear to be support for (typically faster) REST-based updating of LWC bundle files as there is for Aura bundle files. If/when the Tooling API provides support, IC will be updated accordingly. In the interim LWC components are always deployed via the Metadata API.
      • LWC deployment errors are not well-structured at this point. IC currently attempts to process deployment error messages to determine the correct associated source files for accurate error annotation, but there may still be unexpected/unhandled patterns and/or incorrect inference of the associated source file.

1.8.4.3 / 2.0.4.4 release notes

posted Dec 5, 2018, 6:44 AM by Scott Wells

1.8.4.3 / 2.0.4.4

  • Issues 1170/1171 - The previous build's update for the Winter '19/API 44.0 behavioral change around Flow metadata didn't properly take into account projects staying on API versions prior to that. Things should now work properly for pre-44.0 API versions as well as 44.0+ API versions.

1.8.4.2 release notes

posted Dec 4, 2018, 7:49 AM by Scott Wells

1.8.4.2

  • Issue 367 - Fixed a long-standing metadata retrieval issue that would omit server-only metadata in the metadata selection dialog when using Context for the Contents drop-down.
  • Issues 1170/1171 - Updated special handling for Flow metadata in metadata subscriptions based on behavioral changes in Winter '19/API v44.0. You may need to update your metadata subscriptions accordingly.
  • Issue 1173 - Fixed an issue with reference injection in enum constants used as switch labels.
  • Issue 1175 - Corrected MyTerritory and MyTeamTerritory to be My_Territory and My_Team_Territory respectively in SOQL USING SCOPE clauses.
  • Issues 1176/1177 - The fix in 2.0.4.2 for {!...} language injection in XML attribute values was not complete and resulted in a few other issues as a side-effect. Hopefully this is fully addressed now, but don't hesitate to let me know if other related issues are found.
  • Issue 1181 - Added support for offline license deactivation.
  • Added support for multi-line TODO comments in Apex in IntelliJ IDEA/WebStorm 2018.3+.
  • Other minor fixes and performance enhancements.

2.0.4.3 release notes

posted Dec 4, 2018, 7:48 AM by Scott Wells

2.0.4.3

  • Metadata Management Enhancements, Improvements, and Fixes - The main theme of the next several releases will be enhancements, improvements, and fixes for metadata deployment/retrieval/removal, metadata subscription management, Salesforce DX project usage, etc. This release includes the following:
    • Issue 367 - Fixed a long-standing metadata retrieval issue that would omit server-only metadata in the metadata selection dialog when using Context for the Contents drop-down.
    • Issue 743 - Updated the metadata deployer to properly process status updates and errors reported from unit test execution as part of deployment. This does not yet include the ability to specify whether unit tests should be executed during deployment or the specific subset of tests to execute. That enhancement is close behind, though, and will be included in one of the next few builds.
    • Issues 1170/1171 - Updated special handling for Flow metadata in metadata subscriptions based on behavioral changes in Winter '19/API v44.0. You may need to update your metadata subscriptions accordingly.
    • Added a new Salesforce DX configuration option, Enable fast org list. Normally IC uses sfdx force:org:list to enumerate SFDX organizations for integration as IC connections. Because the CLI must verify each org as active and accessible, that command can be quite long-running and therefore disruptive to a smooth development workflow. When this option is enabled, IC instead uses the SFDX JSON config files and lightweight SOQL queries directly against the dev hub orgs to gather the same information. NOTE: This option should be considered beta/experimental for now and is disabled by default. If any issues are found while using this option, please report them with sufficient details to reproduce and, if necessary, disable this option so that the CLI is used for org enumeration.
  • Issue 1173 - Fixed an issue with reference injection in enum constants used as switch labels.
  • Issue 1175 - Corrected MyTerritory and MyTeamTerritory to be My_Territory and My_Team_Territory respectively in SOQL USING SCOPE clauses.
  • Issues 1176/1177 - The fix in 2.0.4.2 for {!...} language injection in XML attribute values was not complete and resulted in a few other issues as a side-effect. Hopefully this is fully addressed now, but don't hesitate to let me know if other related issues are found.
  • Issue 1181 - Added support for offline license deactivation.
  • Added support for multi-line TODO comments in Apex in IntelliJ IDEA/WebStorm 2018.3+.
  • Other minor fixes and performance enhancements.

1.8.4.1 release notes

posted Nov 21, 2018, 12:50 PM by Scott Wells

1.8.4.1

  • Issue 1168 - Added lightning:accordionSection component.
  • Issue 1169 - Fixed a parser issue with {! in HTML/XML comments in Visualforce/Lightning.
  • Fixed an issue with proper language injection for {!...} formulas in HTML/XML string literals. This seems to be a behavioral regression in IntelliJ IDEA/WebStorm as the previous implementation did work in older builds and evidently stopped working at some point recently. The new implementation should work in all builds.
  • Updates required for IntelliJ IDEA/WebStorm 2018.3+.

2.0.4.2 release notes

posted Nov 21, 2018, 12:49 PM by Scott Wells

2.0.4.2

  • Issue 1168 - Added lightning:accordionSection component.
  • Issue 1169 - Fixed a parser issue with {! in HTML/XML comments in Visualforce/Lightning.
  • Fixed an issue with proper language injection for {!...} formulas in HTML/XML string literals. This seems to be a behavioral regression in IntelliJ IDEA/WebStorm as the previous implementation did work in older builds and evidently stopped working at some point recently. The new implementation should work in all builds.
  • Fixed an issue that could occur during OST generation when multiple local .object files are found in the project for the same SObject type.
  • Updates required for IntelliJ IDEA/WebStorm 2018.3+.

1.8.4.0 release notes

posted Nov 12, 2018, 1:07 PM by Scott Wells

1.8.4.0

  • Issue 1056 - Major performance optimization for SOAP API client initialization on first access. If you've ever been annoyed at the long pause the first time Illuminated Cloud makes a call to Salesforce after starting the IDE--and I know that I have!--then you'll likely enjoy this change as it reduces that pause to the bare minimum required for the SOAP client functionality required by Illuminated Cloud. NOTE: I've had a number of people helping to burn in this change over the past month or so, but there is a possibility that changing the SOAP client could break access to some org types. If that's the case, please let me know ASAP so that I can provide access to the previous build until the issue is resolved to avoid any interruption in the ability to use Illuminated Cloud.
  • Issue 1145 - Fixed an issue with rendering of ChangeEvent and Feed objects in the OST. If you have been affected by this issue, you will need to regenerate at least the SObjects portion of your OST after taking this update.
  • Issue 1148 - Fixed an issue that could cause incorrect references to be injected into method invocations when the arguments closely match overloaded method signatures.
  • Issue 1149 - Fixed an issue with rendering of System.SandboxPostCopy into the OST as an Apex class instead of an Apex interface. If you have been affected by this issue, you will need to regenerate your OST after taking this update.
  • Issue 1150 - Added support for lightning:messages.
  • Issue 1158 - Added support for Knowledge objects in the OST. If you have been affected by this issue, you will need to regenerate at least the SObjects portion of your OST after taking this update.
  • Major improvements to the generated documentation headers for SObject fields in the OST. Now most of the field details--data type, constraints, encryption scheme, picklist field values, formulas, default values, etc.--are rendered into the OST and available for integrated API documentation. You will need to regenerate at least the SObjects portion of your OST after taking this update to see these improvements.
  • Fixed an issue that caused substitution rules to be applied to binary files in some cases. This may be a actual fix for issue 865 as well.

2.0.4.1 release notes

posted Nov 6, 2018, 8:28 AM by Scott Wells

2.0.4.1

  • Issue 1148 - Fixed an issue that could cause incorrect references to be injected into method invocations when the arguments closely match overloaded method signatures.
  • Issue 1158 - Added support for Knowledge objects in the OST. If you have been affected by this issue, you will need to regenerate at least the SObjects portion of your OST after taking this update.
  • Issue 1162 - Fixed an issue with the Incomplete Concrete Implementation code inspection when an interface method is implemented via an inheritance relationship.
  • Fixed an issue that caused substitution rules to be applied to binary files in some cases. This may be a actual fix for issue 865 as well.
  • Integrated JSON schema definitions for sfdx-project.json and project-scratch-def.json files. Code completion, validation, and integrated documentation should now be available in these files.
  • Fixed an issue with the new generated SObject field header documentation if the source data contained a block comment ending (*/). If you have been affected by this issue, you will need to regenerate at least the SObjects portion of your OST after taking this update.

1-10 of 65