2.2.6.3 release notes

 2.2.6.3

  • Issue 2325 - Added an option to the Safe navigation operator usage code inspection for whether to warn about usages of the safe navigation operator in operands of relational expressions. While such usages are technically valid, they can result in confusion. This new option is enabled by default, so the inspection will continue to yield the same results as before, but if desired, those specific warnings can now be disabled via either the code inspection settings directly or via contextual intention/quick fix for a warning against a relational expression operand.
  • Issue 2336 - Inconsistent API version code inspection banner messages now take the IDE project frame width into consideration and use abbreviated messages for narrower frames.
  • Issue 2338 - Fixed an issue with CLI-based deployment that would result in No authorization information found for -g due to a regression in the Salesforce CLI's force:source:deploy command. The long-form option (--ignoreerrors) is now used to avoid the current ambiguity with the short-form option (-o).
  • Updated the IcApexDoc integration to support specification of custom Velocity templates for ApexDoc HTML generation as added in 1.0.0.4. This integration includes the following features:
    • You can choose the directory in which custom Velocity templates can be found when generating ApexDoc via the integrated IcApexDoc executor.
    • Provided rich custom Velocity template editing support when IC2 is paired with IntelliJ IDEA Ultimate Edition (unfortunately other JetBrains IDEs don't provide first-class support for Velocity). This includes assistance configuring a Java module for the custom templates directory with the necessary IcApexDoc jars included in the module classpath, automatic addition of the template context variables for code completion and static code analysis, etc. Note that you must have the IcApexDoc bin directory in the system execution path and a Java 11+ SDK configured in the IDE for this assistance to be offered.
    • For those using IC2 with JetBrains IDEs other than Intellij IDEA Ultimate Edition, I've included a simple custom file type, IcApexDoc custom Velocity template, that provides reasonable syntax highlighting and minimal code completion offerings for *.vm files. Note that due to a limitation with IntelliJ IDEA Community Edition, this file type is associated with *.xvmx by default in that IDE. Changing the file type association explicitly to *.vm will enable the file type properly.
  • Fixed an issue resulting from another Salesforce CLI regression where a failed execution of the force:source:push command no longer reports a value for status. It sounds like a proper CLI fix is coming for that regression shortly, but the problem should be addressed by the fix/workaround included in this build of IC2.
  • Fixed an issue with the Annotation and modifier agreement code inspection where it would incorrectly report a method with the @ReadOnly annotation and any one of the @Http* annotations as being invalid.
  • IC2 now detects missing/invalid connections in existing Apex unit test run configurations when they are executed and prompts the user to update the run configuration with the project's configured connection or to open the run configuration settings so that the issue can be corrected explicitly.
  • Fixed an issue with constructor references in ApexDoc @see tags failing to resolve.