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. Until a fix is made available, this may result in an error message of the form "Module is not installed" for custom LWC components referenced via dynamic imports.
- Added limited support for External/Third-party LWC components.
- Issue 2441 - Fixed an issue that occurs during OST generation when a local custom object is found with the same base name as a known namespace.
- Improved code completion when implementing parameterized interfaces. Now the type parameters are added and parameter type completion is triggered automatically.
- Improved the Apex Invalid Type code inspection's detection of incorrect/invalid usage of type parameters.
- Implemented a workaround for IDEA-333629 where, under the bundled Light theme, tooltips that contain code with syntax highlighting applied are unreadable due to low color contrast. In that situation, the code is now rendered for tooltip presentation without syntax highlighting applied.
- Provided a more specific and useful message when Einstein GPT for Developers service authentication fails. In most cases, that occurs because the feature has not been enabled in the target org.