Posts

Showing posts from October, 2023

2.2.8.8 release notes

  2.2.8.8 Issue 2426  - In Apex, it's technically valid to dereference  System.Map.values()  as a single instance of the map's value type, though  only  when the value type is some type of  SObject , e.g.,  accountsByName.values()?.AccountNumber , and  only  when the map has  exactly  one entry. To be blunt, I don't like that allowed idiom for a few reasons. It feels unnecessary and unsafe—pay specific attention to the use of the safe navigation operator before accessing fields of the one-and-only map entry's value—and in order to provide proper support, it muddies the variant code completions offered for the  values()  method to include both instance methods of  System.List  and fields of the map's value type. Having said that, it is allowed and valid, so I've added support for it in IC2's expression type evaluator. Issue 2449  - Added support for email templates created and managed via the Lightning app. Those aren't reported via the Metadata API and m

2.2.8.7 release notes

  2.2.8.7 IDEA-2446  - Fixed an issue with the  PMD Salesforce  code inspection when used with  PMD 7.0.0-rc4 . Note that integration with PMD 7.x may continue to be fragile until the final build is released. In the interim, it should always be safe to use the last official build of PMD,  6.55.0 . IDEA-2447  - Resolved an issue experienced by at least one user where GACK / internal server error was causing OST generation to fail while querying external service metadata. WEB-63263  - In the previous release I referenced a bug I'd logged against JetBrains where custom LWC components referenced in ES6 dynamic imports were not resolving properly. Well, it turns out after a bit more digging, that was my problem to solve. This build includes a fix and those references should now resolve properly. Fixed several small issues that could occur when implementing parameterized system types where the type parameters are used as method formal parameters, most notably the new  System.Comparator  

2.2.8.6 release notes

  2.2.8.6 Issue 2424  - Winter '24 / API v59.0 updates Updated all SOAP API clients to be based on the API v59.0 WSDLs. Updated the API version used for primary communication with Salesforce APIs to 59.0. Added 59.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 v59.0. Updated the OST version number to prompt regeneration for system API changes in API v59.0. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Winter '24 changes. Updated the bundled SLDS CSS and SVG icons to 2.22.0. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Added support for the new  Comparator  interface. Added support for Dynamic LWC components.  NOTE:  I have filed a bug with JetBrains,  WEB-63263 , for an issue I've observed where dynamic imports are not being properly resolved.