2.0.3.2 release notes

posted Aug 10, 2018, 6:53 AM by Scott Wells

2.0.3.2

  • Issue 1075 - Addressed a possible ClassCastException that was introduced with the the work for issue 907.

2.0.3.1 release notes

posted Aug 8, 2018, 9:54 AM by Scott Wells

2.0.3.1

  • Issue 907 - Added tabbed editor support for Lightning bundles and for meta.xml files alongside their corresponding source files. Editor sub-tabs can be navigated from the keyboard using Alt+Shift+Left/Right on Windows/Linux and Ctrl+Shift+Left/Right on Mac.
  • Issue 1036 - Fixed an issue that would cause fields with the same name from different namespaces on packaged custom objects to conflict. Now namespaced fields in the OST are always rendered as the fully-qualified name. NOTE: An OST regeneration is required to realize the benefits of this fix and is highly recommended for all users.
  • Issue 1060 - Fixed an issue with the Extract Method refactoring that could cause closing braces of extracted statement lists to be omitted in the new method.
  • Fixed an issue in WebStorm 2018.2 with auto-completion of JavaScript functions in Lightning markup resulting from a backward-incompatible plugin SDK change.

1.8.3.6 release notes

posted Jul 30, 2018, 8:24 AM by Scott Wells

1.8.3.6

  • Issue 686 - Restructured the way that coverage data is loaded from the Salesforce org for display in the IDE to avoid concurrency/re-entrancy issues. If you see any issues with coverage relating to this change, whether a regression to previous working behavior or a recurrence of the process storm issue that this is intended to put to rest, let me know.
  • Issue 787 - When opening the Log Viewer from an SFDX project, sometimes the wrong connection would be selected initially. Now the SFDX project's scratch org connection should be the initial selection.
  • Issues 851 and 987 - Fixed an issue that could occur when there are multiple SObject types with the same name but different namespaces. Things should complete and resolve properly now when this is the case.
  • Issue 973 - Evidently the way I'd expressed dependencies between the two inheritance-related indices wasn't correct. I've updated the link between them and this problem finally seems to be resolved. If you see further issues with proper linking of inheritance relationships in the IDE after this build, please let me know.
  • Issue 1010 - Fixed an issue with reference injection from Visualforce/Lightning to Apex controller methods.
  • Issue 1011 - Fixed an issue with code completions against inner types not inserting the properly-qualified name based on the insertion context.
  • Issue 1018 - Fixed an issue that would occur when the Log Viewer table is sorted and the wrong log would be loaded when selected.
  • Issue 1021 - Fixed an issue with expression type inference for nested arrays or arrays as type parameters of lists.
  • Fixed an issue that would cause deployment errors reported against files with spaces in their names, e.g., layout metadata, not to hyperlink properly in the Messages view.

2.0.3.0 release notes

posted Jul 30, 2018, 8:24 AM by Scott Wells

2.0.3.0

  • Issue 686 - Restructured the way that coverage data is loaded from the Salesforce org for display in the IDE to avoid concurrency/re-entrancy issues. If you see any issues with coverage relating to this change, whether a regression to previous working behavior or a recurrence of the process storm issue that this is intended to put to rest, let me know.
  • Issue 787 - When opening the Log Viewer from an SFDX project, sometimes the wrong connection would be selected initially. Now the SFDX project's scratch org connection should be the initial selection.
  • Issues 851 and 987 - Fixed an issue that could occur when there are multiple SObject types with the same name but different namespaces. Things should complete and resolve properly now when this is the case.
  • Issue 973 - Evidently the way I'd expressed dependencies between the two inheritance-related indices wasn't correct. I've updated the link between them and this problem finally seems to be resolved. If you see further issues with proper linking of inheritance relationships in the IDE after this build, please let me know.
  • Issue 1010 - Fixed an issue with reference injection from Visualforce/Lightning to Apex controller methods.
  • Issue 1011 - Fixed an issue with code completions against inner types not inserting the properly-qualified name based on the insertion context.
  • Issue 1018 - Fixed an issue that would occur when the Log Viewer table is sorted and the wrong log would be loaded when selected.
  • Issue 1021 - Fixed an issue with expression type inference for nested arrays or arrays as type parameters of lists.
  • Issue 1026 - When creating a new non-SFDX project in WebStorm, the project directory name is now defaulted to reflect the selected connection name until/unless explicitly changed by the user.
  • Issue 1053 - Made Approval.ProcessWorkitemRequest and Approval.ProcessSubmitRequest properly extend Approval.ProcessRequest in the OST. Note that an OST regen will be required before this change will be available.
  • Fixed an issue that would cause deployment errors reported against files with spaces in their names, e.g., layout metadata, not to hyperlink properly in the Messages view.

1.8.3.5 / 2.0.2.9 release notes

posted Jul 23, 2018, 11:40 AM by Scott Wells

1.8.3.5 / 2.0.2.9

  • Issue 1029 - Fixed an issue introduced with skipCodeCoverage support after Summer '18 where an active coverage suite would not be properly reset when tests are run with the Always Collect Coverage option enabled.
  • Issue 1034 - The default dev hub is now always pre-selected in the scratch org creation dialog when more than one dev hub is available.
  • Issue 1038 - Features in scratch org definition files can now be either a comma-delimited list in a single string value or a first-class array.
  • Issue 1039 - When a scratch org definition is loaded from a file, the user is only prompted to save if the values are changed from those that were loaded.
  • The user is no longer required to re-select the connection in the project configuration dialog after recreating one with the same name, in particular when renewing a scratch org with the same alias.
  • Improved error reporting when IC fails to create a trace flag or debug level, in particular due to surpassing the allowed log storage amount.
  • Added a Delete All Logs action to the Log Viewer tool window. Use this with caution as all logs in the org are deleted in response to this action. This is particularly useful when the allowed log storage amount is surpassed and trace flag/debug level configuration is no longer allowed.
  • Accommodated for an issue showing unit test debug logs after a recent logging format change. Please let me know if you still find log information missing after updating to this or a more recent release.
  • Fixed an issue that was causing one-off Apex Offline Debugger run configurations against pasted logs to fail. It should now be possible to debug external logs via explicit run configurations again.

1.8.3.4 / 2.0.2.7 release notes

posted Jul 11, 2018, 7:34 AM by Scott Wells

1.8.3.4 / 2.0.2.7

  • Updated for IntelliJ IDEA/WebStorm 2018.2 backward-incompatible plugin SDK changes. If you find any issues using Illuminated Cloud with 2018.2+ (or for that matter, any previous supported version), please report them to support and they will be addressed ASAP.

1.8.3.3/2.0.2.6 release notes

posted Jul 3, 2018, 8:00 AM by Scott Wells

1.8.3.3/2.0.2.6

  • Issue 978 - Either partial commits never worked via the Tooling API or there has been a recent regression in that functionality. Either way, IC now treats successes reported by otherwise failed container async requests as not having occurred from a state tracking/reporting standpoint. I have raised this issue with Salesforce to determine whether this is original/intentional behavior or a regression. If/when the Tooling API properly supports partial commits, this can be reverted.
  • Issue 1015 - Namespace substitution and deployment/retrieval substitution rules are now applied to static resource bundle contents are they are archived as static resource files for deployment and extracted back into bundles as a result of retrieval respectively.
  • Issue 1020 - Fix for issue where the timestamps used for conflict and dirty tracking might not be computed properly when the org and local workstation are not in the same timezone. This problem was found while working on working on issue 1020 and may or may not be a fix for that bug, but it's certainly something that needed to be addressed.
  • Issue 1024 - Fixed an issue where expired/deleted scratch org information could be cached in memory until the project was closed/reopened or the IDE restarted. Now when a scratch org with a particular alias is replaced, IC should pick up the change immediately.
  • Issue 1040 - Changed lightning:textArea.maxLength to maxlength. As always, the IDE caches the XSDs used for Visualforce/Lightning elements and their attributes aggressively, so you'll likely need to use Ctrl+B/Cmd+B on any existing reference to an element in the lightning namespace to force the cache to rebuild.

1.8.3.2 release notes

posted Jun 11, 2018, 8:23 AM by Scott Wells

1.8.3.2

  • Issue 1002 - Summer '18/API 43.0 updates:
    • API client updated to v43.0 and 43.0 available as a selectable version for configured connections.
    • Full support for the new Apex switch statement including:
      • Grammar update for all variants (literal, enum constant, and SObject)
      • Syntax highlighter
      • Code formatter including new switch-specific configuration settings
      • Full auto-completion support
      • Reference injection for enum constants and SObject types/variables
    • Added support for the new @NamespaceAccessible annotation.
    • Added all new Salesforce DX org shape features (CascadeDeleteContactsToMultipleAccountsStateAndCountryPicklist) for use during scratch org creation.
    • Integrated the new skipCodeCoverage unit test execution option.
      • By default code coverage is now only collected when tests are run explicitly with coverage. Tests executed using standard run or debug actions specify this new option and will not change code coverage metrics. According to Salesforce this should result in a 10-20% decrease in the time required to execute unit tests.
      • This behavior can be configured as desired using the Illuminated Cloud>Configure Application>Unit Tests and Code Coverage>Always Collect Code Coverage configuration option.
    • Added completion and integrated API documentation support for the new UITheme.getUITheme() Visualforce function.
    • Updated all affected bundled frameworks and libraries:
      • Lightning standard component library XSDs for all new and updated components
      • SLDS to 2.6.0
      • Aura JavaScript interfaces to latest
      • Integrated API docs for everything except for Lightning components. Lightning component documentation has changed significantly in this release so v42.0 component docs are still bundled. A future release will accommodate for these documentation changes.
    • NOTE: Report and dashboard subfoldering is currently not fully supported. The metadata enumeration APIs do not currently seem to return sufficient information about folder/subfolder relationships. I have reported this to Salesforce and will update the product for full support as soon as the API provides the required information.
    • NOTE: Due to additions and changes to Apex system types, it is strongly recommended that you regenerate the OST for each project when it is opened for the first time after this update. If you find that expected Summer '18 types are missing or incorrect in the OST, please regenerate it before reporting issues. If issues remain after an OST update, report them via the public issue tracker and they'll be resolved in short order.

2.0.2.5 release notes

posted Jun 11, 2018, 8:18 AM by Scott Wells

2.0.2.5

  • Issue 1002 - Summer '18/API 43.0 updates:
    • API client updated to v43.0 and 43.0 available as a selectable version for configured connections.
    • Full support for the new Apex switch statement including:
      • Grammar update for all variants (literal, enum constant, and SObject)
      • Syntax highlighter
      • Code formatter including new switch-specific configuration settings
      • Full auto-completion support
      • Reference injection for enum constants and SObject types/variables
      • Illegal assignment inspection enhancements
    • Added support for the new @NamespaceAccessible annotation.
    • Added all new Salesforce DX org shape features (CascadeDeleteContactsToMultipleAccountsStateAndCountryPicklist) for use during scratch org creation.
    • Integrated the new skipCodeCoverage unit test execution option.
      • By default code coverage is now only collected when tests are run explicitly with coverage. Tests executed using standard run or debug actions specify this new option and will not change code coverage metrics. According to Salesforce this should result in a 10-20% decrease in the time required to execute unit tests.
      • This behavior can be configured as desired using the Illuminated Cloud>Configure Application>Unit Tests and Code Coverage>Always Collect Code Coverage configuration option.
    • Added completion and integrated API documentation support for the new UITheme.getUITheme() Visualforce function.
    • Updated all affected bundled frameworks and libraries:
      • Lightning standard component library XSDs for all new and updated components
      • SLDS to 2.6.0
      • Aura JavaScript interfaces to latest
      • Integrated API docs for everything except for Lightning components. Lightning component documentation has changed significantly in this release so v42.0 component docs are still bundled. A future release will accommodate for these documentation changes.
    • NOTE: Report and dashboard subfoldering is currently not fully supported. The metadata enumeration APIs do not currently seem to return sufficient information about folder/subfolder relationships. I have reported this to Salesforce and will update the product for full support as soon as the API provides the required information.
    • NOTE: Due to additions and changes to Apex system types, you will be prompted to update the OST for each project when it is opened for the first time after this update. It is recommended that you perform this update, minimally for system classes and ideally also for SObject types. If you find that expected Summer '18 types are incorrect in the OST, please regenerate the OST before reporting issues. If issues remain after an OST update, please report them via the public issue tracker and they'll be resolved in short order.

2.0.2.4 release notes

posted Jun 4, 2018, 7:25 AM by Scott Wells

2.0.2.4

  • More Offline Apex Debugger fixes and improvements, in particular when stepping into and through system methods, e.g., into a Comparable implementation when calling List.sort().
  • Added special support for CaseComment and its fields which are not included in metadata API listMetadata() calls.
  • Fixed an issue with namespace substitution against alternative connections in the SOQL Query and Anonymous Apex tool windows.

1-10 of 46