2.0.9.5 release notes

posted Dec 6, 2019, 7:18 AM by Scott Wells

2.0.9.5

  • Issue 821 - I finally broke down and filled in the gaps in the OST around system types that either aren't included in the Tooling API completions resource or are included with untyped properties. The one notable exception is the ConnectApi namespace which was updated as much as possible given the limited documentation available, but many properties still lack type information. Otherwise all properties should now be strongly-typed, and the totally missing DataSource namespace types should now be present and accurate.
    • NOTE: You must regenerate your offline symbol table to pick up these changes.
  • Issue 1481 - Added full support for ApexDoc @see references to members as well as types. Members should work properly for code completion, reference injection, and quick documentation. Note that because @see references only include the method name and not signature, overloaded methods will result in multiple reference injections.
  • Issue 1483 - Any pending native connection changes are now applied before Salesforce DX orgs are created or removed.
  • Issue 1484 - Fixed an issue that could occur if an invalid path is specified for the Salesforce CLI. Now when the executable fails, the user is prompted to choose a valid executable path instead of being bombarded with error messages.
  • Fixed an issue with the connection status bar widget that prevented it from popping up when no project files are open.
  • Some icons have been changed in preparation for JetBrains' 2020.* deprecation/removal cycle.
  • Other fixes and improvements.

2.0.9.4 release notes

posted Nov 25, 2019, 11:29 AM by Scott Wells   [ updated Nov 25, 2019, 11:50 AM ]

2.0.9.4

  • Improved LWC ES6 import live templates:
    • importitems - Works exactly as before to import one or more exports from a module of the form import { items } from 'module';
    • importdefault - Works exactly as before to import the default export from a module of the form import alias from 'module';
    • importapex - Imports an @AuraEnabled Apex class member of the form import alias from '@salesforce/apex/class.member';
    • importobject - Imports an SObject of the form import alias from '@salesforce/schema/sobject';
    • importfield - Imports an SObject field of the form import alias from '@salesforce/schema/sobject.field';
    • importlightning - Imports one or more exports from a standard Lightning component of the form import { items } from 'lightning/component';
    • importcomponent - Imports one or more exports from a custom Lightning component of the form import { items } from 'c/component';
    • importresource - Imports a static resource URL of the form import alias from '@salesforce/resourceUrl/resource';
    • importasset - Imports a content asset URL of the form import alias from '@salesforce/contentAssetUrl/asset';
    • importlabel - Imports a custom label of the form import alias from '@salesforce/label/label';
    Note that the short-lived importitems2 and importdefault2 live templates have been removed.
  • Improved code completion and reference injection for custom labels. References now resolve to the actual label name in the respective *.labels[-meta.xml] file, and only valid code completions for labels in a given context are presented. Note that for some reason references in package.xml files and LWC component markup files do not show up properly in Find Usages. I am still researching that and hope to fix it in a near-term build.
  • Issue 1471 - Fixed an infrequent issue with creation of intermediate temporary directories.
  • Issue 1477 - Fixed an issue with the unresolvable method signature against methods defined in a trigger.
  • Issue 1479 - Prospective fix for issue with reading an XML element outside of a read action.
  • Fixed issues with incremental deployment state tracking for individual custom labels.

2.0.9.3 release notes

posted Nov 14, 2019, 10:05 AM by Scott Wells

2.0.9.3

  • Lightning Web Components enhancements
    • Code completion for all Salesforce-specific ES6 import types:
      • Standard modules
      • Standard (lightning namespace) components
      • Custom components (must reside in project)
      • @AuraEnabled Apex symbols (must reside in project)
      • Schema objects and fields
      • Static resources and content assets (must reside in project)
      • Custom labels (must reside in project)
      • I18N information
    • Reference injection/navigation for all imported modules and symbols (commercial base IDEs only; not available in Community Edition base IDEs).
      • NOTE: - This ensures that renames of ES6 symbols, Apex symbols, static resources, and content assets propagate to the respective import statement references in LWC ES6 source.
    • New live templates for ES6 import creation:
      • importitems - Creates an import { b } from 'a'; statement stopping at a and then b respectively. This live template has already been available in commercial base IDEs but is now also available in Community Edition base IDEs.
      • importitems2 - Creates an import {  } from 'a'; statement stopping at a and allowing further code completion of the imported module. Use importitems when importing from a fully-qualified name, e.g., lwc or @salesforce/user/Id, and importitems2 when importing from the stem of other names, e.g., @salesforce/apex/ or @salesforce/schema/.
      • importdefault - Creates an import b from 'a'; statement stopping at a and then b respectively. This live template has already been available in commercial base IDEs but is now also available in Community Edition base IDEs.
      • importdefault2 - Creates an import  from 'a'; statement stopping at a and allowing further code completion of the imported module. Use importdefault when importing from a fully-qualified name, e.g., lwc or @salesforce/user/Id, and importdefault2 when importing from the stem of other names, e.g., @salesforce/apex/ or @salesforce/schema/.
    • Improved JavaScript/ES6 syntax highlighting in Community Edition IDEs when *.js is associated with the JavaScript Files (Improved Syntax Highlighting) file type. Community Edition IDE users are prompted to switch to the new file type after initial update to this version of the plugin or higher.
    • Added a module validation rule to exclude .sfdx/typings to remove resolution ambiguity.
  • Fixed an issue with incorrect reporting of LWC deployment errors in non-scratch org projects. Reported errors should again be properly linked to the corresponding source code.
  • Other fixes and improvements.

2.0.9.2 release notes

posted Nov 8, 2019, 6:39 AM by Scott Wells

2.0.9.2
  • Reverted the TurboActivate update due to a bug. The vendor is now aware of this issue and I'll update again once a fix has been issued.
  • Issue 1463 - Partial fix. Now the error message from a failed SFDX project creation is properly displayed to the user.
  • Other fixes and improvements.

2.0.9.1 release notes

posted Oct 30, 2019, 8:38 AM by Scott Wells

2.0.9.1

  • Refactored the SFDX-dev-against-any-org deployer to use the Salesforce CLI to submit the deployment job and IC's native deployer to provide ongoing status and results. This provides much more detailed deployment and test execution progress information and works around a number of deployment error reporting bugs in the Salesforce CLI.
  • Deployment, retrieval, and removal success information in the Messages view is now hyperlinked to the corresponding source files.
  • Added No Namespace and No Ancestors options to the scratch org creation dialog.
  • Added online help links pointing to the User Guide for the following:
    • Application-level configuration
    • License management
    • Apex code style configuration
    • Scratch org creation
    • OAuth connection creation
    • Metadata subscription management
    As new topics are added to the User Guide, they will be similarly integrated into the online help system.
  • Fixed a recent regression in method and call hierarchies caused by an incompatible plugin SDK change.
  • Fixed a recent regression to the top-level Apex type/trigger rename refactoring that prevented the type/trigger with the old name from being removed from the organization.
  • Fixed an issue that could cause unit tests to be reported as ignored/skipped when they have completed successfully but the log couldn't be retrieved.
  • Updated to TurboActivate 4.1.9.0.
  • Other fixes and improvements.

1.8.5.5 release notes

posted Oct 18, 2019, 6:53 AM by Scott Wells

1.8.5.5

  • Issue 1438 - Added PartnerCommunity as a valid SFDX feature.
  • Issue 1446 - Fixed an issue that could cause entries to be duplicated in the Apex structure view when inherited members are shown.
  • Issue 1447 - Autoscroll-from-source now works properly in the Apex structure view.
  • Issue 1451 - Added missing types from the Auth namespace. This change requires OST regeneration.
  • Issue 1453 - Fixed an issue with scratch org creation when no settings or org preferences are specified and an empty org preferences section is included in the resulting scratch org definition file. In the next build I'll completely remove support for org preferences.
  • Restored TerritoryManagement as a valid SFDX feature.
  • Made System.AccessType an enum instead of a class in the OST. This change requires OST regeneration.

2.0.9.0 release notes

posted Oct 18, 2019, 6:52 AM by Scott Wells

2.0.9.0

  • Issue 1410 - Added support for Territory2Model/Territory2/Territory2Rule as a pseudo-decomposed metadata type.
  • Issue 1438 - Added PartnerCommunity as a valid SFDX feature.
  • Issue 1443 - Build success dates are no longer updated from Compare With Server actions.
  • Issue 1446 - Fixed an issue that could cause entries to be duplicated in the Apex structure view when inherited members are shown.
  • Issue 1447 - Autoscroll-from-source now works properly in the Apex structure view.
  • Issue 1449 - Fixed a layout issue with the build options dialog on lower resolution screens.
  • Issue 1451 - Added missing types from the Auth namespace. This change requires OST regeneration.
  • Issue 1453 - Fixed an issue with scratch org creation when no settings or org preferences are specified and an empty org preferences section is included in the resulting scratch org definition file. In the next build I'll completely remove support for org preferences.
  • Restored TerritoryManagement as a valid SFDX feature.
  • Made System.AccessType an enum instead of a class in the OST. This change requires OST regeneration.

1.8.5.4 release notes

posted Oct 14, 2019, 10:56 AM by Scott Wells

1.8.5.4 - Winter '20 / API v47.0 Update

  • Updated SOAP clients from API v47.0 WSDLs.
  • Updated the internal API version to 47.0.
  • Added 47.0 as an explicitly-selectable API version in the connection manager.
  • Added support for the $MessageChannel Visualforce global variable and lightning:messageChannel Aura component.
  • Added Winter '20 scratch org features for use in the scratch org creation dialog.
  • Updated the bundled SLDS CSS to 2.10.0.
  • Updated metadata.xsd to v47.0 for code completion and validation in XML metadata files.
  • Updated all bundled API documentation.
  • Other minor changes and improvements.

2.0.8.9 release notes

posted Oct 14, 2019, 10:03 AM by Scott Wells

2.0.8.9 - Winter '20 / API v47.0 Update

  • Updated SOAP clients from API v47.0 WSDLs.
  • Updated the internal API version to 47.0.
  • Added 47.0 as an explicitly-selectable API version in the connection manager.
  • Updated all LWC standard components for code completion and validation.
  • Added support for the $MessageChannel Visualforce global variable and lightning:messageChannel Aura component.
  • Added Winter '20 scratch org features for use in the scratch org creation dialog.
  • Updated the Salesforce DX JSON schema files for sfdx-project.json and *-scratch-def.json code completion and validation.
  • Updated the bundled SLDS CSS to 2.10.0.
  • Updated metadata.xsd to v47.0 for code completion and validation in XML metadata files.
  • Updated all bundled API documentation.
  • Incremented the OST version number to prompt users to update their OSTs for Winter '20 changes.
  • Other minor changes and improvements.

2.0.8.8 release notes

posted Oct 9, 2019, 11:13 AM by Scott Wells   [ updated Oct 9, 2019, 11:14 AM ]

2.0.8.8
  • Issue 1444 - Fixed an issue when deploying LWC components with tests in a traditional module.

1-10 of 120