2.2.0.6 release notes

 2.2.0.6

  • Issue 2038 (redux) - The parser fix for 2038 had a small ripple effect that could cause some odd behavior with Apex class, constructor, and enum constant declarations and references to those declarations. This ripple effect should now be properly addressed.
  • Issue 2043 - Added missing custom SObject extensions to the list used to determine if a qualified name is namespace__name or name__customObjectExtension, specifically for Big Objects, Knowledge Articles, and Knowledge Article Versions. This addresses issues with proper name resolution for custom objects of these types
  • With the broad rollout of MFA now occurring, native connections may become less and less of a viable option as there's currently no way to handle the additional authentication factors. Instead OAuth connections should be used. Now when authentication fails for a native connection with certain well-known error types, IC2 includes additional messaging about MFA and the potential need to switch to OAuth.
  • There's been some confusion and consternation about the removal of the Deploy all modified files sub-option of the Deploy on save option in 2.2.0.5. This is now being tracked as issue 2048. You can see full details and monitor progress in the linked issue, but the short version is that the Deploy all modified files option never quite worked the way it was intended due to the way that the base JetBrains IDEs fire save notifications. The Deploy Modified Metadata action is a more definitive and reliable option for updating an org based on locally-changed files. I'm currently considering allowing the deploy-on-save behavior to be configurable with the following options:
    • The current behavior which is unconditional deployment of all selected files (most often just the file for the current editor) on explicit end user-initiated saves.
    • The current behavior plus the Deploy Modified Metadata action behavior, but without any intermediate dialog or other steps required, and you'd also be able to select the scope of such deployments as Module, Module and dependencies, or Project when selecting this option for the deploy-on-save behavior.
    Note that in either case an explicit end user-initiated save results in deployment of all selected files regardless of whether those files are out-of-date or up-to-date relative to the org. The second option also includes any other files in the configured scope that are out-of-date relative to the org in the same deployment. I'm likely going to move the timing of this enhancement forward so that those who have come to expect more of a "bring up-to-date" behavior to the deploy-on-save action can once again have it, albeit in a more reliable form than previously.