2.2.7.5 release notes

 2.2.7.5

  • Issue 1543 - The generated OST now includes @NamespaceAccessible symbols from installed unlocked packages with the same namespace as the current project, and IC2 now properly resolves references to those symbols and offers them as code completions. Note that the OST must be regenerated to see the effect of this change.
  • Issue 2376 - Added support for PMD 7, specifically PMD 7.0.0-rc3. A few comments and considerations:
    • Because of differences in the Java APIs for PMD 6.x and 7.x, supporting both for real-time static code analysis in a single integration is a bit tricky. The integration has been tested extensively, but it's certainly possible that issues may be found. If so, please report them in the IC2 public issue tracker with as much diagnostic data as possible.
    • For the same reason, the recommended versions of PMD are going to be specifically 6.55.0 and 7.0.0-rc3. As new PMD 7 builds are released, I will update IC2 as appropriate. Hopefully the API has stabilized by this point, though.
    • I have noticed that PMD 7 fails to load some ruleset files that PMD 6 loaded without issue, specifically those that contain Code Climate properties. IC2 should now convey all errors reported during ruleset loading to the end user.
  • Issue 2378 - Added support for CSS and JS language injection for <aura:html tag='style|script'> tags respectively.
  • Issue 2386 - Improved filtering of SObject fields in SOQL SELECT lists.
  • Issue 2398 - Added small as a valid option for lightning-button-menu's icon-size attribute. Marked lightning-combobox's validity attribute as not required.
  • Fixed an issue that could result in an orphaned Salesforce CLI process (and therefore a blocked TCP port) when OAuth connection creation is explicitly canceled by the user.
  • Fixed an issue where the OST would generate while pushing to a scratch org as part of module resolution.

NOTE: During OST generation you may be seeing longer times when querying the Apex system/standard types, or you may even see that step fail one or more times and and then ultimately succeed upon retry. I am in active discussion with Salesforce about these issues. They have identified the root causes (there are evidently multiple contributing problems) and are investigating potential solutions. I will update IC2 as appropriate based on these solutions (if updates are even necessary) and will post progress in Issue 2400 and also here as part of the standard release notes.