2.2.7.1 release notes

 2.2.7.1

  • NOTE: I have been seeing intermittent failures with the Salesforce completions?type=apex Tooling REST API that is used during offline symbol table generation. These are reported as generic HTTP 500 / Server Error and seem to resolve themselves on repeated OST generation attempts or attempts after doing just about anything in the org, e.g., performing a successful deployment. I have made Salesforce aware of these failures and they are investigating, but I also wanted to ensure that users were also aware of them and possible workarounds until the issues are properly resolved.
  • Issue 2367 - Added support for the DigitalExperienceBundle metadata type. Note that this explicitly ignores the DigitalExperience sub-type for purposes of deployment and retrieval at present and operates at the bundle-level only.
  • Issue 2368 - Fixed an issue where Apex string literals wouldn't be properly escaped when used directly with the sdv, sdvj, and sdjv postfix templates.
  • Issue 2369 - Fixed a regression in the Apex Method can be made 'static' inspection that was accidentally introduced in 2.2.7.0 and would result in false positives.
  • Issue 2370 - Added proper support for all Aura API and library components including:
    • lightning:conversationToolkitAPI
    • lightning:empApi
    • lightning:navigationItemAPI
    • lightning:notificationsLibrary
    • lightning:omniToolkitApi
    • lightning:overlayLibrary
    • lightning:quickActionAPI
    • lightning:utilityBarAPI
    • lightning:workspaceAPI
    When these components are used in Aura markup and then "imported" into Aura JavaScript using component.find(componentAuraId), the resulting expression now properly implements the interface of the imported API or library.
    NOTE: There seems to be an issue with proper type inference for Promise type parameters, reported as WEB-61395 in JetBrains' public issue tracker. That can affect proper typing of the resolved Promise value when calling these APIs.
  • Salesforce CLI issue 2095 - The problems for a failed push or pull are now placed in the JSON list property data and not the original list property result. IC2 now allows for either and should once again properly display all issues (specifically conflicts) for a failed push or pull.