Illuminated Cloud Announcements

  2.2.5.7 Issue 2314  - Spring '23 / API v57.0 updates Updated all SOAP API clients to be based on the API v57.0 WSDLs. Updated the API version used for primary communication with Salesforce APIs to 57.0. Added 57.0 as an available API version number for configured connections. Updated  metadata.xsd  used for validation and code completion in metadata XML files to API v57.0. Updated the OST version number to prompt regeneration for system API changes in API v57.0. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Spring '23 changes. Updated the bundled SLDS CSS and SVG icons to 2.20.1. Updated all integrated API documentation. Added full support for  Database.*WithBinds()  signatures including code completion and reference resolution against keys in the provided bind map. Verified setup of the  UTAM Generator  in commercial JetBrains IDEs as follows: Add a  utam  dependency in  package.json  (using th...

  2.2.5.6 Apex postfix completion template enhancements Added support for creation of  custom  Apex postfix completion templates. A demonstration video is available  here . Added the following new Apex postfix completion templates: Test assertions at  - Wraps the expression in  Assert.isTrue() . af  - Wraps the expression in  Assert.isFalse() . ae  - Wraps the expression in  Assert.areEqual() . ane  - Wraps the expression in  Assert.areNotEqual() . aio  - Wraps the expression in  Assert.isInstanceOfType() . anio  - Wraps the expression in  Assert.isNotInstanceOfType() . an  - Wraps the expression in  Assert.isNull() . ann  - Wraps the expression in  Assert.isNotNull() . Statements if  - Adds a check verifying that a boolean expression is  true . else  - Adds a check verifying that a boolean expression is  false . switch  - Adds a  switch  statement for v...

  2.2.5.5 Issue 1474  - Fixed an issue with Apex class file templates configured to behave as live templates. Now an Apex class created against a live template-enabled file template with at least one user-populated variable must be finished or cancelled before file creation post-processing steps such as supporting  meta.xml  file creation, automatic subscription updates, and automatic deployment are performed. As part of this work I also extended the template-based file creation features to allow the use of live template macros for the template variables. Because there's no first-class auxiliary metadata mechanism for these variables, I've extended the templating system to allow them to be specified in the template itself using comments of the form: // <variableName>.[expression|defaultValue|alwaysStopAt]=<value> The order of template variable evaluation is based on the order of these directives if present or the order of the variable usages themselves in...