Posts

2.3.2.2 release notes

2.3.2.2 Unlocked support for JetBrains' 2024.2 builds which are currently in an  EAP (Early Access Program)  state. Note that while IC2 can now be installed into these builds, I  strongly discourage  using them until an  official  build is released, likely at the end of July or beginning of August. Pre-release builds often include breaking changes to the plugin SDK. I'm unlocking support to avoid a catch-22 that can occur when JetBrains begins rolling out official builds of a new version without a compatible IC2 build already available in the plugin repository. I will update IC2 as necessary between now and the official 2024.2 release with any changes required for breaking plugin SDK changes. If you decide to brave these waters and run into issues, please feel free to  report them  in the  public issue tracker  so that I can address them, and then  revert  to the most recent  supported official build  of 2024.1. Issue...

2.3.2.1 release notes

2.3.2.1 Completely removed support for Salesforce Functions  - I  mentioned  that this would be coming about a month ago, and IC2 has been prominently displaying a banner in the  Salesforce Functions  tool window requesting that any users who were still wrapping up work in that area let me know that they still needed it for a bit longer. I haven't heard from anyone, so support for Salesforce Functions has been removed completely starting with this build. Issue 2593  - Fixed an issue with execution of tests from individual Apex unit test classes with a  @TestSetup  method against an org with a namespace. Prospective fix for the "No components were retrieved" message after successful retrieval of new metadata on Mac and Linux. Minimally there's significantly better diagnostic logging if the problem is still present, but hopefully the included fix will put that issue to rest once and for all. Fixed an NPE that could occur during validation of ApexDoc...

2.3.2.0 release notes

2.3.2.0 Issue 2565  - Eliminated a  large  set of "Slow operations are prohibited on the EDT" warnings by changing the way that key IDE project/module information is requested by IC2. This should be an effective no-op for end users and is more about having IC2 play nicely in the JetBrains IDE plugin model. I've had a small set of kind users helping to burn in these changes over the past ~2 months, reporting issues as they've found them and helping to verify the corresponding fixes (which in some cases took repeated attempts). I'd like to  personally thank  all of the users who were willing to endure — and provide invaluable diagnostic information for — issues in these test builds. Their patience and generous donations of their valuable time are  greatly appreciated ! If new issues are found  that were not present in previous builds without these changes,  please report them ASAP  with as much diagnostic information as possible (though of cour...

2.3.1.9 release notes

2.3.1.9 Issue 2584  - Summer '24 / API v61.0 updates Updated all SOAP API clients to be based on the API v61.0 WSDLs. Updated the API version used for primary communication with Salesforce APIs to 61.0. Added 61.0 as an available API version number for configured connections. Updated the OST version number to prompt regeneration for system API changes in API v60.0. Updated the bundled  completions?type=apex  Tooling REST API response to be based on the API v61.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '24 changes. Updated the bundled SLDS CSS and SVG icons to 2.24.2. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Added full support for the new Apex  @InvocableVariable  annotation  DefaultValue  and  PlaceholderText  attributes. I've also updated the Apex Annotation and Modifier Agreement code in...

2.3.1.8 release notes

2.3.1.8 Reissue of  2.3.1.7  with the fix for a potential error resulting from a stale cache entry when collecting transitive dependencies/dependents for Apex unit test execution and/or coverage analysis. 

2.3.1.7 release notes

  2.3.1.7 JetBrains has issued patch-level updates for all of their 2023.1+ IDEs to fix a  security issue . Please see the linked information for details, but the short version is that the security issue should only affect those using JeBrains' GitHub pull request integration. Nonetheless, I  strongly  encourage all users update to a JetBrains IDE version with this fix ASAP. More improvements to the recent dependencies-/dependents-based enhancements for Apex unit test execution and code coverage analysis: All transitive dependencies and dependents are now collected at the member-level instead of the file-level. Again, this means that the resulting set of dependencies/dependents should be as small and focused as possible short of performing runtime data flow analysis. When using the new "changed-only" features, this should ultimately mean less time spent waiting for unrelated unit tests to execute and a more focused view of impacted code coverage. Added many more meta...

2.3.1.6 release notes

2.3.1.6 This week's build is a small set of bug fixes. I'm in final testing of the last anticipated major round of Apex unit testing and code coverage dependency/dependent-related enhancements. They didn't quite make this week's build but should be in great shape for next week's. Issue 2572  - Fixed an issue with SOQL query count validation for pure aggregate queries that return a single row. Issue 2576  - Fixed an NPE during expression type evaluation reported by a user. Issue 2580  - Improved original error message retention when handling caught exceptions during PMD execution. Fixed a recently-introduced regression where file delete handler logic wasn't firing properly. This would result in removal of supporting meta.xml files and the corresponding metadata from the server not happening when metadata files were removed locally from the project. Added another user-reported variant of  FIELD_INTEGRITY_EXCEPTION  when trying to deploy an LWC JavaScript file via ...